feat: handle rate limiter code 429 by back-off retry #80
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
santhoshramaraj
requested review from
mure,
spanglerco and
cameronwaterman
as code owners
|
Superseded by #90 as giving the user the flexibility to handle retry is better than hardcode it. |
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.
What does this Pull Request accomplish?
Implement a basic back-off retry method for
DataFrameClientto handle status code 429 by the rate limiter.Why should this Pull Request be merged?
Simplify user-side handling for http status code 429
What testing has been done?
TODO: Detail what testing has been done to ensure this submission meets requirements.