[retries] Allow specifying status codes to retry on #3
Conversation
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
Octocrab's retry logic is... less than ideal. We need to handle both 401 and 429 statuses, so just allow an array of status codes to be checked against. If one wanted this to be more generic, they could thread some extra types and such through, but that feels like a bigger thing to do than what I have here.
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.
Octocrab's retry logic is... less than ideal. We need to handle both 401
and 429 statuses, so just allow an array of status codes to be checked
against. If one wanted this to be more generic, they could thread some
extra types and such through, but that feels like a bigger thing to do
than what I have here.