-
Notifications
You must be signed in to change notification settings - Fork 36
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
Abuse rate limitation needs an update #437
Closed
dontcallmedom opened this issue
Sep 6, 2021
· 2 comments
· Fixed by #438 · May be fixed by jeffhubLR/create-pull-request#1
Closed
Abuse rate limitation needs an update #437
dontcallmedom opened this issue
Sep 6, 2021
· 2 comments
· Fixed by #438 · May be fixed by jeffhubLR/create-pull-request#1
Comments
dontcallmedom
added a commit
to dontcallmedom/plugin-throttling.js
that referenced
this issue
Sep 6, 2021
Woah, good catch! Thank you for reporting it and for sending a pull request! |
🎉 This issue has been resolved in version 3.5.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
dontcallmedom
added a commit
to w3c/validate-repos
that referenced
this issue
Sep 6, 2021
dontcallmedom
added a commit
to w3c/validate-repos
that referenced
this issue
Sep 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current code to detect hitting of the abuse rate limit reads:
As far as I can tell, nowadays, the error message from github reads:
You have exceeded a secondary rate limit. Please wait a few minutes before you try again.
So the test should be updated accordingly.
The text was updated successfully, but these errors were encountered: