Concurrency Limits decrease in response to 429, 503 and 500s #513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generate changelog in
|
- Reduce the number of available concurrency limits in response to 429's and 500's
+ Reduce the number of available concurrency limits in response to 429's and 5xx's |
|
Released 0.19.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR
We would only reduce the number of limits if the server returned an explicit 429.
After this PR
==COMMIT_MSG==
Reduce the number of available concurrency limits in response to 429's and 500's
==COMMIT_MSG==
I could go either way on whether general 500's should result in reduced concurrency limits.
Possible downsides?