-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(http): Force default rate limits for some known hosts #30207
feat(http): Force default rate limits for some known hosts #30207
Conversation
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.
Do you have a source for the new rate limit numbers?
Maybe the project has documentation that says: "please limit to x
requests per y
time"?
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.
otherwise LGTM
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
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.
I'm happy with the test descriptions now. I'll let the maintainers review the rest.
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
This PR seems to be the only blocker for #27369 |
🎉 This issue has been resolved in version 37.439.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
rubygems.org
https://crates.io/api
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: