You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When creating a skeleton query pack using the extension, the following error is logged to the "CodeQL Extension Log":
Could not create skeleton QL pack: Parsing output of Adding and installing java pack dependency. failed: Unexpected token 'P', "Package in"... is not valid JSON
However, it seems adding the pack was actually successful, but the extension erroneously expected JSON output from the CodeQL CLI when the output seems to be plaintext (?).
In the CodeQL tab under "Queries" click "Create one to get started", or alternatively run the command "> CodeQL: Create Query"
Select "Java" as language
Open the "CodeQL Extension Log" and scroll to the end
❌ Bug: You see the error mentioned above being logged
Expected behavior
No error should be logged
Additional context
In general the query pack logging output seems to be quite verbose. Is that intended?
Probably not a big problem though because I assume users are normally not expected to look at "CodeQL Extension Log" except for troubleshooting.
The text was updated successfully, but these errors were encountered:
Describe the bug
When creating a skeleton query pack using the extension, the following error is logged to the "CodeQL Extension Log":
However, it seems adding the pack was actually successful, but the extension erroneously expected JSON output from the CodeQL CLI when the output seems to be plaintext (?).
Version
Extension:
VS Code:
To reproduce
❌ Bug: You see the error mentioned above being logged
Expected behavior
No error should be logged
Additional context
In general the query pack logging output seems to be quite verbose. Is that intended?
Probably not a big problem though because I assume users are normally not expected to look at "CodeQL Extension Log" except for troubleshooting.
The text was updated successfully, but these errors were encountered: