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

Parse errors, no idea how to find the files #12828

Open
Haarolean opened this issue Apr 14, 2023 · 5 comments
Open

Parse errors, no idea how to find the files #12828

Haarolean opened this issue Apr 14, 2023 · 5 comments
Labels
question Further information is requested

Comments

@Haarolean
Copy link

I got the following issue during one of the scans:

Could not process some files due to syntax errors
View workflow run
A parse error occurred: Comments are not legal in JSON.. Check the syntax of the file. If the file is invalid, correct the error or exclude the file from analysis.

CodeQL also found 2 other warnings like this. See the workflow log for details.

The thing is, it's impossible to find the problematic files within the workflow log:
| Diagnostic | Summary |
+---------------------------------------------------+------------------------+
| Extraction errors | 13 results (13 errors) |
| Could not process some files due to syntax errors | 3 results (3 warnings) |
| Successfully extracted files | 548 results |

That's kinda it, I couldn't find the mentioned files there.

@Haarolean Haarolean added the question Further information is requested label Apr 14, 2023
@jketema
Copy link
Contributor

jketema commented Apr 14, 2023

Hi @Haarolean,

Thanks for your question. Where do you see the A parse error occurred: message? I am not able to locate it.

@Haarolean
Copy link
Author

@jketema thanks for the quick reply!

This is located under the "security" tab in the repo.
image

@jketema
Copy link
Contributor

jketema commented Apr 14, 2023

Thanks!

I think this is a shortcoming in our tooling, where it does not actually output the error to the log. It'll let the relevant team know about this.

In the mean time, you might try enabling CodeQL debugging on the workflow (see here). Thus will produce a number of artifacts, including all logs and a copy of the database that is being built. You might want to check whether those logs do include the relevant details.

@Haarolean
Copy link
Author

Thank you!

@jketema
Copy link
Contributor

jketema commented May 15, 2023

The problem with finding the logs remains, I believe, but the actually error you're getting here should be resolved by #12951. This fix should be part of the CodeQL 2.13.2 release.

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

No branches or pull requests

2 participants