This repository has been archived by the owner on Mar 22, 2021. It is now read-only.
github api rate limit exhaustion #81
Comments
|
One snag is that AFAICT GitHub doesn't provide any way to visualize what requests were made, which would've been a nice debugging tool. So the three users of the token are:
GHPRB is probably a big consumer too, yeah. Without being able to use webhooks, it needs to be able to rescan PRs when polling to look for changes. AFAICT, the GitHub API library it uses doesn't make use of conditional requests. |
jlebon
added a commit
to jlebon/release
that referenced
this issue
Jan 15, 2018
We're currently hitting against our token API limit for @rh-atomic-bot, which is causing merge issues across all projects that PAPR supports. We have to rework our infrastructure so that this is no longer an issue, though in the meantime, I'd like to temporarily drop automated testing of FAH on openshift-ansible so that other PAPR projects can be more reliable. See also: projectatomic/papr#81
|
We're hitting this every hour right now. As a short-term workaround, I've submitted a request to drop testing for openshift-ansible: openshift/release#550. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've been hitting this periodically.
We may need to dive into figuring out what's actually using the key; offhand guess is homu's "check all outstanding PRs for mergability after a merge" is part of the problem
Also https://developer.github.com/v3/#conditional-requests
homu probably isn't doing that, and i wouldn't be surprised if jenkins isn't either
The text was updated successfully, but these errors were encountered: