-
Notifications
You must be signed in to change notification settings - Fork 5.1k
fix(client): honor Retry-After delays up to two minutes #3555
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
Merged
+111
−9
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d2c6924
fix(client): honor long Retry-After delays
tescherm-openai 6e55b90
fix(client): bound Retry-After delays to one day
tescherm-openai 8d149be
fix(client): ignore invalid Retry-After dates
tescherm-openai 05b8ddf
fix(client): cap Retry-After at two minutes
tescherm-openai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,3 +12,4 @@ | |
|
|
||
| INITIAL_RETRY_DELAY = 0.5 | ||
| MAX_RETRY_DELAY = 8.0 | ||
| MAX_RETRY_AFTER_DELAY = 2 * 60 | ||
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When automatic retries are enabled, a non-retryable error such as HTTP 400 can now raise
ValueErrororOverflowErrorinstead ofAPIStatusErrorif it carries a syntactically parseable but out-of-range date, such asRetry-After: Fri, 29 Sep 100000 16:26:57 GMT:parsedate_tz()accepts it, butmktime_tz()in_parse_retry_after_header()fails. Previously_should_retry()did not parse this header for statuses that would not be retried, so conversion failures should be treated as malformed header values rather than escaping from this new call.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
parsedate_tz()can accept dates thatmktime_tz()cannot represent, so I updated_parse_retry_after_header()to treatTypeError,ValueError,OverflowError, andOSErroras malformed header values. I also added sync and async regressions confirming that an HTTP 400 with this date still raisesAPIStatusErrorafter one request, plus timeout-calculation coverage for the fallback behavior. The fix is committed locally as8d149be8and has not been pushed yet.