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

Intermittent failure on graphQLHandler.setup #1000

Open
pnacht opened this issue Oct 31, 2022 · 1 comment
Open

Intermittent failure on graphQLHandler.setup #1000

pnacht opened this issue Oct 31, 2022 · 1 comment

Comments

@pnacht
Copy link
Contributor

pnacht commented Oct 31, 2022

The error given is:

internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: non-200 OK status code: 502 Bad Gateway body: "{\n "data": null,\n "errors":[\n {\n "message":"Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include 04C0:42FC:18AD2A3:328AC33:6358827B when reporting this issue."\n }\n ]\n}\n"

I've seen #784, but this is running @v2.0.3.

Observed in pytorch a week ago. They have since disabled the Action because of these intermittent failures pytorch/pytorch#87740, so I cannot determine if the failures would still be ongoing.

The run linked to above is currently on page 8 of runs, but it's a very active repo, so may be further down the list by the time you read this!

However, just a day before, there were no such failures (see page 10 of runs). Was this an instability in the graphQL API or an underlying bug?

@spencerschrock
Copy link
Contributor

We see a related error in about 10% of graphQL queries. Still need to dig deeper, but my best guess is some sort of instability on the graphql API or we're close to a processing timeout which makes the call fail intermittently.

I can take another look since this is causing issues for repos

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

2 participants