Skip to content

feat: add retry-after-limit#6

Merged
gera2ld merged 10 commits into
violentmonkey:mainfrom
sylingd:main
May 22, 2026
Merged

feat: add retry-after-limit#6
gera2ld merged 10 commits into
violentmonkey:mainfrom
sylingd:main

Conversation

@sylingd
Copy link
Copy Markdown
Contributor

@sylingd sylingd commented May 8, 2026

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:

image

A new retry-after-limit parameter has been added. If the request can be retried (a retry-after header exists) and the retry time is less than the retry-after-limit parameter, the request will be re-initiated after waiting for retry-after seconds.

@sylingd
Copy link
Copy Markdown
Contributor Author

sylingd commented May 21, 2026

Hi @gera2ld can you process this PR when you have time?

Copy link
Copy Markdown
Member

@gera2ld gera2ld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR.
However, I don't really understand why we need those fields. Could you explain more about your use cases?

Comment thread src/types.ts Outdated
Comment thread src/types.ts Outdated
@sylingd sylingd changed the title feat: add throttled-retry and onStatusChange feat: add throttled-retry May 22, 2026
@sylingd sylingd changed the title feat: add throttled-retry feat: add retry-after-limit May 22, 2026
Comment thread src/index.ts
Comment thread src/types.ts Outdated
@gera2ld gera2ld merged commit 4027c9b into violentmonkey:main May 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants