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
Builds failing - REST API returning 202 and never 200. #45
Comments
Please see pull request #46 as I believe that I might have fixed this error. |
I resolved the 202 error that kept reporting according to your Pull Request #46. But there is still a little problem here: Can you fix the problem? |
Ah yeah, I see the problem. Seems there's also a problem with the stars as I definitely do not have 8k stars 😂 |
Okay, it seems that when That means my fix just bypasses the part where it gets lines of code changed, essentially, by causing all repos to 404. The problem is that the API never returns a 200 after sending a 202, so could this be an issue on GitHub's side, and not actually the code? Stats that use the GraphQL API instead work fine as far as I know. |
Even though the API paths aren't correct in github-stats, the correct paths don't work either. That definitely looks like an API bug. Not even the example from the documentation works: $ curl -i -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/octocat/hello-world/stats/contributors
HTTP/2 202
server: GitHub.com
date: Sun, 22 Aug 2021 18:30:55 GMT
content-type: application/json; charset=utf-8
content-length: 5
x-github-media-type: github.v3; format=json
access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset
access-control-allow-origin: *
strict-transport-security: max-age=31536000; includeSubdomains; preload
x-frame-options: deny
x-content-type-options: nosniff
x-xss-protection: 0
referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
content-security-policy: default-src 'none'
vary: Accept-Encoding, Accept, X-Requested-With
x-ratelimit-limit: 60
x-ratelimit-remaining: 57
x-ratelimit-reset: 1629660598
x-ratelimit-resource: core
x-ratelimit-used: 3
x-github-request-id: BB1E:12FC:550C0B:61B2A6:612297DF
{
} I have reported the bug to GH |
Thank you for reporting the bug @theCalcaholic, however, I have checked the API paths in github-stats today and they do seem to match the documentation. ( It does definitely seem like a GitHub bug. |
Ah, you're right! Turns out I broke the path myself and fixed it again later :D |
Haha, you wouldn't believe the number of times I've done that trying to figure this out 😂 |
Github Docs
|
As far as I know, these APIs all return 202: |
Okay, after undoing my "fix that wasn't a fix", it seems that GitHub has now fixed this issue as my image has now generated correctly, so I shall close the issue. Thanks guys! |
I've been quietly following this thread, but haven't had time to chime in. Glad it's resolved, at least for the moment! I'll be sure to link back to this if others are having similar problems. |
Queries erroring with code 202.
When the Action to generate images is run, it sits endlessly and keeps throwing out "A path returned 202. Retrying..." and "There were too many 202s. Data for this repository will be incomplete.".
I suspect this might be a side effect of the changes to the OAuth API, as shown here: https://www.githubstatus.com/incidents/6gpzw3mdnkwj
Status on the API itself seems fine.
I have checked in multiple of the forked repos and have seen the same issue occurring, after spending ages trying to figure out if it was mine 😂
The text was updated successfully, but these errors were encountered: