When GitHub response is 403 or 429, only backoff ratelimit if message…#359
Merged
ezyang merged 1 commit intoMay 28, 2026
Merged
Conversation
ezyang
approved these changes
May 28, 2026
… indicates Solves an issue I had where my OAUTH token didn't have appropriate permissions to open pull requests, but I didn't know because the error messages were being swallowed by secondary rate limit handling.
auto-merge was automatically disabled
May 28, 2026 17:32
Head branch was pushed to by a user without write access
benjaminglass1
force-pushed
the
fallthrough_non_ratelimit_errors
branch
from
6ace818 to
4704aef
Compare
Contributor
Author
|
@ezyang Fixed the linter issue. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
… indicates
Solves an issue I had where my OAUTH token didn't have appropriate permissions to open pull requests, but I didn't know because the error messages were being swallowed by secondary rate limit handling.