-
Notifications
You must be signed in to change notification settings - Fork 17
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
ERROR:ghastoolkit.octokit:GraphQL API Status :: 502 results into workflow failure #140
Comments
@tr1shul thanks for reporting this bug. You are the 4th person to bring it up. It is a problem with the GraphQL query we are using to get licence information. I plan on having a patch out for this along with a Code Scanning bug fix next week. |
@GeekMasher thank you. Any update on this fix? |
@GeekMasher Still getting the error, here's the raw logs:
|
GraphQL is not needed in our use case. We want to apply policies only to code scanning alerts and secret scanning then get a successful build job if the policies are not violated. Is there a set of recommended flags I can set in order to disable GraphQL and enable only what's needed? |
What happened?
I encountered a 502 error on the GraphQL API while attempting to set up policy-as-code on a repository. The error message logged is: ERROR:ghastoolkit.octokit:GraphQL API Status :: 502.
The issue arose during the process of configuring a workflow where, upon every code push, CodeQL would scan the code, and after the scan completed, the policy-as-code configuration would trigger. The expected outcome was that if the policy returned a success, the code would be allowed to merge into the repository. However, the actual behavior deviated from this, as the policy-as-code setup consistently failed with a 502 error on the GraphQL API, blocking the entire workflow.
To troubleshoot the problem, I tested the same policy-as-code configuration on a smaller repository. Interestingly, this test was successful, with the setup running without encountering any errors. This led me to believe that the issue might be related to the size of the repository or specific configurations (magit/forge#20 (comment)).
I have attached the YML configuration file and the raw logs from the failed run for further examination.
Given the critical nature of this issue, which is blocking code merging workflows in our development process, I request that the 502 error in the GraphQL API be investigated. Any guidance on resolving this issue or suggestions for alternative configurations to avoid such errors would be greatly appreciated.
Version
v2 (current major version)
Where are you experiencing the issue?
GitHub Actions
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: