-
Notifications
You must be signed in to change notification settings - Fork 56
feat: implement rate limit handling for Vercel API requests #718
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
Conversation
Added a new `vercel_request` function to manage API requests with automatic retries on rate limiting. Updated existing API calls to use this function for improved reliability in handling rate limits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request implements rate limit handling for Vercel API requests by introducing a new vercel_request wrapper function with automatic retry logic. The implementation aims to improve reliability when interacting with the Vercel API by automatically retrying requests that encounter rate limiting.
Changes:
- Added
vercel_requestfunction with retry logic for handling HTTP 429 rate limit responses - Updated three existing Vercel API calls (DELETE, GET, POST) to use the new wrapper function
- Added
timemodule import to support sleep delays between retries
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…r logging Signed-off-by: rohan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 7 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🔍 Overview
Added a new
vercel_requestfunction to manage API requests with automatic retries on rate limiting. Updated existing API calls to use this function for improved reliability in handling rate limits.Addresses #679
💡 Proposed Changes
💚 Did You...