Allow robust to use the server-suggested Retry-After header #37
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.
Description
The Retry-After HTTP response header indicates how long the user agent should wait before making a follow-up request. This PR allows to use the server-suggested retry_after value and is implemented as an opt-in feature to avoid breaking changes.
The HTTP specification allows Retry-After to be provided either as a delay in seconds or as a date. I believe the latter is out of scope for this use case, which motivates the try/except used to convert the string to a float.
Side note: The Data Stores Service does provide a Retry-After value with 429 errors.
Contributor Declaration
By opening this pull request, I affirm the following: