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

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
Copy link
Contributor

The current code to detect hitting of the abuse rate limit reads:

      if (/\babuse\b/i.test(error.message)) {

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.

@gr2m
Copy link
Contributor

gr2m commented Sep 6, 2021

Woah, good catch! Thank you for reporting it and for sending a pull request!

@gr2m gr2m added the bug label Sep 6, 2021
@gr2m gr2m closed this as completed in #438 Sep 6, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Sep 6, 2021

🎉 This issue has been resolved in version 3.5.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment