Jx: GitHub API quotas being exceeded

[tdcox]

Looks like we are starting to run up against GitHub API quota limits, which seem to be capped at 5,000 calls per hour.

12:02:30 GitHub API Usage: Current quota has 3375 remaining (593 over budget). Next quota of 5000 in 59 min. Sleeping for 9 min 55 sec.
12:05:30 GitHub API Usage: The quota may have been refreshed earlier than expected, rechecking...
12:05:30 GitHub API Usage: Current quota has 3375 remaining (406 over budget). Next quota of 5000 in 56 min. Sleeping for 6 min 54 sec.

Not sure why this reports 3375 remaining but then says is over budget and sleeps. Mismatched values somewhere in the checks?

[stevef1uk]

I am hitting the same issue. I installed jx on minikube, stopped minikube & restarted and my local install is not at all happy!

started by timer
[Wed Sep 26 15:38:00 UTC 2018] Starting branch indexing...
15:38:00 Connecting to https://api.github.com with no credentials, anonymous access
15:38:04 GitHub API Usage: Current quota has 44 remaining (3 over budget). Next quota of 60 in 49 min. Sleeping for 7 min 42 sec.
15:41:04 GitHub API Usage: Still sleeping, now only 4 min 42 sec remaining.
15:44:04 GitHub API Usage: Still sleeping, now only 1 min 42 sec remaining.
15:45:46 GitHub API Usage: Current quota has 42 remaining (0 under budget). Next quota of 60 in 42 min
15:45:46 Connecting to https://api.github.com with no credentials, anonymous access
Examining stevef1uk/environment-devourerriver-production

Checking branches...
15:45:49 GitHub API Usage: Current quota has 41 remaining (1 over budget). Next quota of 60 in 42 min. Sleeping for 4 min 34 sec.
15:48:49 GitHub API Usage: Still sleeping, now only 1 min 34 sec remaining.

[haoshuwei]

me too

Started by user admin
[Wed Oct 24 04:10:11 UTC 2018] Starting branch indexing...
04:10:11 Connecting to https://api.github.com with no credentials, anonymous access
04:10:12 GitHub API Usage: Current quota has 3 remaining (38 over budget). Next quota of 60 in 41 min. Sleeping until reset.

[ccojocar]

This issue is mitigated in the serverless jenkins, which does not required to poll the GitHub API.

[pmuir]

Also work on jx git apis should also improve the work see #2641 and #2669

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[hervelemeur]

/remove-lifecycle stale rotten

What can we do if not in serverless?

[renatomariscal]

Does anyone know how to explain the (apparent) mismatch in numbers? Current quota has >0 remaining and it still goes to sleep.

[lasote]

Exactly, I don't understand either.

[charan28]

@renatomariscal @lasote The total quota for the hour is 5000. The plugin is trying to make sure you stay within quota by calculating how much time in the hour has gone by. For example, if you are 45 minutes away from a refresh in quota, the plugin expects you to have 3/4 of your quota, or 3750 (45/60*5000) available. If you only have 3700 available, it won't make an API call.

I'm not saying I agree with the implementation, but that's how it works.

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.