Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix invalid partner #242

Merged
merged 1 commit into from
Aug 30, 2023
Merged

Fix invalid partner #242

merged 1 commit into from
Aug 30, 2023

Conversation

geir-waagboe
Copy link
Contributor

Dette håndterer den første problemet rapporert av e-mottak.

@geir-waagboe geir-waagboe requested a review from a team as a code owner August 29, 2023 11:39
@@ -59,7 +59,7 @@ class PartnerinfoClient(
COUNT_CALL_PARTNERINFO_MULTIPLE_RESPONSE.increment()
}

return response.maxByOrNull { it.partnerId }
return response.minByOrNull { it.partnerId }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ser ut til at den del problemer blir forårsaket av duplikate partnerId'er i oppslag vi syfopartnerinfo. Kan se ut som det dukker opp nye feilaktige partnerId'er sporadisk, og hvis disse er større enn den opprinnelige vi hadde er det bedre å bruke minBy i stedet for maxBy.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Har grav litt mer i dette, og tror ikke mønsteret er så klart - så reverterer denne endringen før merge.

@geir-waagboe geir-waagboe force-pushed the fix-invalid-partner-id branch from 8510314 to 62d2469 Compare August 30, 2023 13:52
@geir-waagboe geir-waagboe merged commit 3811421 into master Aug 30, 2023
3 checks passed
@geir-waagboe geir-waagboe deleted the fix-invalid-partner-id branch August 30, 2023 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants