feat: add retry-after-limit#6
Merged
Merged
Conversation
Contributor
Author
|
Hi @gera2ld can you process this PR when you have time? |
gera2ld
reviewed
May 21, 2026
Member
gera2ld
left a comment
There was a problem hiding this comment.
Thanks for the PR.
However, I don't really understand why we need those fields. Could you explain more about your use cases?
gera2ld
reviewed
May 22, 2026
gera2ld
reviewed
May 22, 2026
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
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.
AMO limits the frequency of API calls. When the limit is exceeded, a 429 error is returned, requiring a retry after a certain period of time. Such as:
A new
retry-after-limitparameter has been added. If the request can be retried (aretry-afterheader exists) and the retry time is less than theretry-after-limitparameter, the request will be re-initiated after waiting forretry-afterseconds.