feat: add rate limit handling with automatic retry for OpenRouter API#14
Open
feat: add rate limit handling with automatic retry for OpenRouter API#14
Conversation
Add global rate limit state tracking per model/endpoint and implement retry logic with exponential backoff for 429 responses. Parse `x-ratelimit-reset` and `x-ratelimit-remaining` headers to coordinate wait times across concurrent requests. Retry up to 5 times with calculated delays based on reset timestamps or exponential backoff (1s, 2s, 3s, etc.). Track rate limit state in Map keyed by `apiBase|model` to prevent redundant requests when
Contributor
Author
|
dont merge yet. I will be bulletproofing this later today to ensure this is the final PR for this functionality |
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.
Add global rate limit state tracking per model/endpoint and implement retry logic with exponential backoff for 429 responses. Parse
x-ratelimit-resetandx-ratelimit-remainingheaders to coordinate wait times across concurrent requests. Retry up to 5 times with calculated delays based on reset timestamps or fallback to exponential backoff (1s, 2s, 3s, etc.) in case outputs aren't successfully parsed. Non-invasive and non-breaking.All tests passed: