-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add support for primary rate limits #4
Comments
Following the discussion in #9 - will be implemented using x-ratelimit-resource (and perhaps a fallback for endpoint-based heuristics, because x-ratelimit-resource isn't officially documented).
|
bump :) |
@NorseGaud nice to see interest. I'd love to hear more about your use case (and hopefully, I'll get to it soon) |
Apparently, code search rate limits behave like primary rate limits (i.e., the response is a primary rate limit error), @NorseGaud @abhijit-hota - I haven't forgotten about this issue and I'm planning to do it soon. My days are pretty busy now, and I'm finishing off async-pagination support now, and then I'm gonna address this one. |
@gofri any update on this topic? |
@Sawthis Edit: not sure if you heard the news about Iran attacking israel, but there might be some more delay after all 😅 |
Unlike secondary rate limits, primary rate limits are long and categorized.
As a result, sleeping is not obviously the natural response for them, and the implementation must be aware of the categories.
Options (not mutually exclusive):
The text was updated successfully, but these errors were encountered: