feat(safe): handle 429 rate limit responses with automatic retry#25
Merged
feat(safe): handle 429 rate limit responses with automatic retry#25
Conversation
Member
Savid
commented
Jan 23, 2026
- Add dynamic rate limiter that pauses on 429 and restores after delay
- Parse Retry-After header, default to 5s if not present
- Retry request once after rate limit wait period
- Add tests for 429 handling, context cancellation, and default delay
- Add dynamic rate limiter that pauses on 429 and restores after delay - Parse Retry-After header, default to 5s if not present - Retry request once after rate limit wait period - Add tests for 429 handling, context cancellation, and default delay
samcm
approved these changes
Jan 23, 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
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.