Skip to content
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

202 (Accepted) HTTP response; backoff and retry #3

Open
ntwb opened this issue Jun 16, 2016 · 3 comments
Open

202 (Accepted) HTTP response; backoff and retry #3

ntwb opened this issue Jun 16, 2016 · 3 comments

Comments

@ntwb
Copy link

ntwb commented Jun 16, 2016

Hi, I've been getting the following error for the past couple of days, I originally thought it was because I was hitting the GitHub API limit for the API key I'm using but I no longer think thats the case (you see an actual message from GitHub telling you you hit the API limit for the day)

Here is what I'm seeing:

This 1st part has taken a couple of days to get past the GitHub API limit and is now cached and appears to work as expected:

I160616 22:28:43.982757 cmd/fetch.go:53  fetching GitHub data for repository repo/repo

I160616 22:28:43.983038 fetch/query.go:258  querying stargazers of repository repo/repo
*** 1,687 stargazers

I160616 22:28:45.206165 fetch/query.go:278  querying user info for each of 1,687 stargazers...
*** user info for 1,687 stargazers

I160616 22:28:45.926333 fetch/query.go:292  querying followers for each of 1,687 stargazers...
*** 68,389 followers (43,406 unique) for 1,687 stargazers

I160616 22:28:48.995858 fetch/query.go:320  querying starred repos for each of 1,687 stargazers...
*** 363,191 starred repos (90,747 unique) for 1,687 stargazers

I160616 22:29:43.917686 fetch/query.go:352  querying subscribed repos for each of 1,687 stargazers...
*** 85,739 subscribed repos (80,406 unique) for 1,687 stargazers

Now, this is what I see everytime I get to the point of retrieving the commits for each stargazer:

I160616 22:29:58.653527 fetch/query.go:384  querying contributions to subscribed repos for each of 1,687 stargazers...
*** 5,432 commits from 360 repos (376 qual, 2,331 total) for 24 stargazers
E160616 22:30:01.925974 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:03.852227 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:05.772839 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:07.251432 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:08.789207 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:11.659565 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:13.708287 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:17.708606 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:20.987420 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry
E160616 22:30:25.068810 fetch/fetch.go:117  202 (Accepted) HTTP response; backoff and retry

Occasionally it will throw the following:

E160616 22:30:26.070563 fetch/fetch.go:127  unable to fetch "https://api.github.com/repos/whatwg/html/stats/contributors"

Apologies, if anything here is n00bish, I installed Go for the 1st time to play with this repo 😄

@spencerkimball
Copy link
Owner

No, not noobish. I've gotten similar errors. Something weird going on with GitHub's API Not sure what the cause is...I mostly just ignored them.

@ntwb
Copy link
Author

ntwb commented Jun 17, 2016

Thanks, I've fired it up again and I'll let it run and see what happens 😬

@DrMegavolt
Copy link

I believe Github just don't have this data right now. so it says 202 "I got it, working now, pls try later" and handling is correct - schedule retry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants