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(gateway): don't skip retry policy with retry methods (backport of #6896) #6900

Merged
merged 1 commit into from Jun 1, 2023

Conversation

kumahq[bot]
Copy link
Contributor

@kumahq kumahq bot commented Jun 1, 2023

Automatic cherry-pick of #6896 for branch release-2.1

Generated by action

cherry-picked commit 87f57df

1. The logic was wrong - if there is ***NO*** retry policy, we should
   skip applying retriable methods, not the other way around
2. Before it might crash with nil pointer dereference when we provided
   httpMethods, but there was no retry policy

Signed-off-by: Bart Smykla <bartek@smykla.com>
@kumahq kumahq bot requested review from a team, slonka and jakubdyszkiewicz and removed request for a team June 1, 2023 10:15
@kumahq kumahq bot added the release-2.1 label Jun 1, 2023
@bartsmykla bartsmykla merged commit 28db678 into release-2.1 Jun 1, 2023
7 checks passed
@bartsmykla bartsmykla deleted the chore/backport-release-2.1-6896 branch June 1, 2023 10:41
lukidzi pushed a commit that referenced this pull request Jun 7, 2023
…6896) (#6900)

1. The logic was wrong - if there is ***NO*** retry policy, we should
   skip applying retriable methods, not the other way around
2. Before it might crash with nil pointer dereference when we provided
   httpMethods, but there was no retry policy

Signed-off-by: Bart Smykla <bartek@smykla.com>
Signed-off-by: Lukasz Dziedziak <lukidzi@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant