-
Notifications
You must be signed in to change notification settings - Fork 80
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
Response code 429 (Too Many Requests) on successComment #361
Comments
Thanks for reporting this @vgropp! You can disable the new feature by setting the Other than that I think it would make sense to add proper handling of such cases to this plugin. |
…c-release#361 If got receives a response code 429 - too many requests - it will retry up to three times for GET and POST requests. This uses the retry API https://github.com/sindresorhus/got/blob/main/documentation/7-retry.md
…c-release#361 If got receives a response code 429 - too many requests - it will retry up to three times for GET and POST requests. This uses the retry API https://github.com/sindresorhus/got/blob/main/documentation/7-retry.md
…c-release#361 If got receives a response code 429 - too many requests - it will retry up to three times for GET and POST requests. This uses the retry API https://github.com/sindresorhus/got/blob/main/documentation/7-retry.md
I got this error today. Never happened before. [5:32:08 PM] [semantic-release] [@semantic-release/gitlab] › ✘ An error occurred while posting comments to related issues and merge requests: |
Got this error last week |
Getting this error now |
Just ran into this as well: https://gitlab.com/marge-org/marge-bot/-/pipelines/1554783088 Not a big deal though as the rest of the release is done before and this probably only happens when not releasing often or on the first release when it spams all the issues/MRs. |
Got this error today |
If all the recent issues reported here are happening on gitlab.com, it could also be that their infrastructure has changed to more aggressive rate limits that the client can't always handle properly anymore. |
@OZIOisgood @jakec-dev @schraal @liz72703 Do you remember whether the errors happened on the first release, when |
We could try to increase the maximum number of retries, similar to how it was originally suggested in #728 (comment). Right now /cc @JonasSchubert |
@fgreinacher Yes, for our team this only occurs on the first release. Subsequent releases are fine. |
🎉 This issue has been resolved in version 13.2.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Folks, please upgrade to 13.2.3 where we increased the default retry limit from 2 to 3. You can also play with the new |
We are running into the gitlab API limit on some projects when multiple semantic-releases are running at the same time from share IPs.
As far as I understand the code
gitlab/lib/success.js
Line 72 in 3051799
Another Option would be rate limiting the requests, but that seems like a lot more work but more sustainable solution.
The text was updated successfully, but these errors were encountered: