-
Notifications
You must be signed in to change notification settings - Fork 474
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
BUG: List GitHub commit crashing for pytorch/pytorch #3464
Comments
I'm noticing the same issue intermittently - sometimes I get results, sometimes not. When I set The GraphQL handler calls GitHub's GraphQL endpoint here: scorecard/clients/githubrepo/graphql.go Line 204 in 846fb19
In GraphQL, scorecard/clients/githubrepo/graphql.go Line 198 in 846fb19
But I don't think commit depth alone is the culprit, we could also try playing with the parameters here: scorecard/clients/githubrepo/graphql.go Lines 30 to 37 in 846fb19
|
Oh, right! Thanks for the info, Raghav! As you said, it's probably because the data returned is too large in this case. I believe playing with the pullRequestsToAnalyze and other parameters may be the right direction here, instead of commit depth. |
Describe the bug
The query that lists GitHub commits is crashing for pytorch/pytorch and possibly affecting the results of multiple checks that depend on this information, such as CI-Tests. CI-Tests is currently resulting in "no pull request found", but manually analysing there are PRs.
Reproduction steps
Steps to reproduce the behavior:
Expected behavior
I expected Scorecard to detect the commits.
Additional context
The text was updated successfully, but these errors were encountered: