Handle float Retry-After headers #117
Merged
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
paulomarg
force-pushed
the
allow_float_retry_after
branch
from
a5c3bb0 to
55dc410
Compare
teddyhwang
approved these changes
Nov 30, 2021
paulomarg
force-pushed
the
allow_float_retry_after
branch
from
55dc410 to
270942c
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
WHY are these changes introduced?
Fixes #115
Our code was working under the assumption that the
Retry-Afterheader would always be an integer, but it can be a float at times.WHAT is this pull request doing?
Casting the float back to an integer after we convert it to microseconds, since at that point any remaining fractional value is irrelevant.
Type of change
Checklist