We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we are expecting that GitHub response will always contain reset time for ratelimit, which isn't true when GitHub returns 403.
There are several options to deal with this:
anitya.lib.backends.github
check_service
RateLimitException
The text was updated successfully, but these errors were encountered:
Fix crash when GitHub returns 403
fbbf6bb
Fixes fedora-infra#832 Signed-off-by: Michal Konečný <[email protected]>
415e223
Fixes #832 Signed-off-by: Michal Konečný <[email protected]>
Successfully merging a pull request may close this issue.
Currently we are expecting that GitHub response will always contain reset time for ratelimit, which isn't true when GitHub returns 403.
There are several options to deal with this:
anitya.lib.backends.github
looks like quick solution)check_service
has it anyway, so it will know when to check the projects again, just raiseRateLimitException
without time.The text was updated successfully, but these errors were encountered: