Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic Rate Limit Handling (Issue #233) #292

Closed

Conversation

devin-ai-integration[bot]
Copy link
Contributor

Implements automatic rate limit detection by dynamically parsing "Retry-After" headers from 429 responses.

Key changes:

  • Add retry_after_seconds to StatusTracker for dynamic wait times
  • Extract Retry-After header from OpenAI rate limit responses
  • Extract Retry-After from LiteLLM RateLimitError
  • Update base processor to use dynamic retry times
  • Add comprehensive test coverage for rate limit handling
  • Fall back to default pause time if no Retry-After header

Fixes #233

Link to Devin run: https://app.devin.ai/sessions/da2f0535ae6b49019aaf990015072300

- Add retry_after_seconds to StatusTracker for dynamic wait times
- Extract Retry-After header from OpenAI rate limit responses
- Extract Retry-After from LiteLLM RateLimitError
- Update base processor to use dynamic retry times
- Fall back to default pause time if no Retry-After header

Fixes #233
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add "(aside)" to your comment to have me ignore it.
  • Look at CI failures and help fix them

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@RyanMarten RyanMarten changed the base branch from dev to main January 6, 2025 23:04
@RyanMarten RyanMarten closed this Jan 11, 2025
@vutrung96 vutrung96 deleted the devin/1735432012-dynamic-rate-limit branch January 15, 2025 16:14
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.

Automatically detect the rate limits
1 participant