-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
github api rate exceeded #908
Comments
@casperdcl, this is a known issue with Travis-CI. There's nothing we can do. We can't migrate to .COM because ppc64le is only available on .ORG. |
@isuruf thanks a lot for you repsonse. is this:
|
It's 2. Note that this happens to all members of conda-forge. If you weren't a member of @conda-forge, but you were a member of 2 orgs each with 3K repos, you'd still have this issue. Travis-CI synchronizes the permissions of each user every day I think and for each repo in each org that the user is a part of, they try to get the permission that you have and if you get write access for a repo, then your permissions in travis-ci is also updated. This is 1 API call per repo and therefore 8K calls are made. |
Our automation is also being hit by this. Is there a known workaround? |
you can buy a higher api limit |
Really? How do you do that? |
I feel like a possible work-around would be if GitHub could increase the API rate for @conda-forge members... It's a little ridiculous that open source devs are being penalised for being open source devs. I'm seriously considering leaving the @conda-forge org to avoid this issue. |
This is probably fixed for non-@conda-forge/core members. I removed read access for all repositories and you should have permissions only for the repositories you maintain. Your first Travis-CI sync will still exhaust your github api rate, but subsequent ones shouldn't. (That's what I think should happen if my guess about how Travis-CI uses the token is correct) |
Ok, though that still sounds like it would be impossible to complete the initial sync then. After 5k is exhausted, will it resume the sync for the remaining 3k 1 hour later? |
I think you'll have to manually start the sync 1 hour later (Or wait 24 hours and Travis-CI will do it for you) |
I think Travis-CI persists the state after each call, otherwise we wouldn't get permission earlier on travis-ci. So, a re-run should work. |
@isuruf I hope this issue can be closed then. Was incredibly hard to debug and involved multiple support tickets with 3 different companies. I'm going to lie down now :) |
Let's keep this open until we can confirm that this works. If you don't see any repositories you don't maintain in https://travis-ci.org/organizations/conda-forge/repositories, then we can close this. I can't test because I have write access to all 8k+ repos. |
hmm says "Last synced about a minute ago" when I hover over the "Sync account" button, and still has 339 pages under "Legacy Services Integration" for conda-forge. Afraid to click "Sync account." |
@casperdcl, did this get fixed? |
I still have 342 pages on https://travis-ci.org/organizations/conda-forge/repositories but haven't encountered the rate limit error recently. |
Issue:
conda-forge making excessive GitHub API calls (hitting the rate limit of 5,000/hr) using all conda-forge user's tokens via "Travis CI for Open Source."
It's unclear if this is an issue with Travis or with conda-forge or both. It's killing all my automation which depends on being able to access the GitHub API.
Details about issue:
-- @casperdcl, Oct 24, 00:40 UTC
-- MK (Travis CI), Oct 23, 12:05 EDT
-- Dominic Jodoin (Travis CI), Oct 3, 16:50 EDT
-- @casperdcl, Oct 3, 09:00 EDT
The text was updated successfully, but these errors were encountered: