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

Stop automatic retrying on RateLimitExceeded #210

Merged
merged 1 commit into from Sep 19, 2022

Conversation

LKaemmerling
Copy link
Member

It does not make sense to retry when the rate limit is already exceeded. However, it makes sense to retry on Conflict. In the best case this would happen on the Caller/User side, but removing the retry completely would be a breaking change.

Signed-off-by: Lukas Kämmerling lukas.kaemmerling@hetzner-cloud.de

@LKaemmerling LKaemmerling force-pushed the stop-retrying-on-rate-limit-exceeded branch 2 times, most recently from f7af2cb to a185597 Compare September 19, 2022 11:48
It does not make sense to retry when the rate limit is already exceeded. However, it makes sense to retry on Conflict. In the best case this would happen on the Caller/User side, but removing the retry completely would be a breaking change.

Signed-off-by: Lukas Kämmerling <lukas.kaemmerling@hetzner-cloud.de>
@LKaemmerling LKaemmerling force-pushed the stop-retrying-on-rate-limit-exceeded branch from a185597 to 3f0b473 Compare September 19, 2022 11:51
@4ND3R50N 4ND3R50N self-requested a review September 19, 2022 11:53
@LKaemmerling LKaemmerling merged commit ba4bea1 into main Sep 19, 2022
Copy link
Contributor

@4ND3R50N 4ND3R50N left a comment

Choose a reason for hiding this comment

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

LGTM

@LKaemmerling LKaemmerling deleted the stop-retrying-on-rate-limit-exceeded branch September 19, 2022 11:53
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.

None yet

2 participants