-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
Frequent "429 TOO MANY REQUESTS" errors from nur-update #186
Comments
This error comes from heroku. I am using a free instance right now. Maybe it is hitting some limits? Has anybody else seen this happen? |
The number of requests don't seems excessive. I have other apps that certainly get more requests. |
I also see now other people having this problem:
|
Could be also API limits from travis ci... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My GitLab CI job frequently fails due to
erroring out with the message
See https://gitlab.com/rycee/nur-expressions/pipelines for the historic runs (the jobs with two stages are the ones pinging nur-update).
Even though the nur-update service gives the 429 error, the update still seems to happen in the NUR repo. For example 8044a5a corresponds to the failing job https://gitlab.com/rycee/nur-expressions/-/jobs/438621162.
I think my repo does hit nur-update more frequently than most NURs, though. Should I try fixing my CI job to avoid curling more than once a day or so?
The text was updated successfully, but these errors were encountered: