Skip to content

/ codeql-cli-binaries

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

Jump to bottom

codeql database interpret-results: Confusing (and possibly wrong) error message NO_KIND_SPECIFIED #20

Open
hmakholm opened this issue Mar 5, 2020 · 1 comment
Open

codeql database interpret-results: Confusing (and possibly wrong) error message NO_KIND_SPECIFIED #20

hmakholm opened this issue Mar 5, 2020 · 1 comment
Labels
CLI bug

Comments

@hmakholm
Copy link
Contributor

@hmakholm hmakholm commented Mar 5, 2020

Copied from github/codeql#2997, filed by @khanhbnv-0950:

i truy codeql database analyze <src-database-js> ql/javascript/ql/src/Security/ --format=csv -o test.csv, but i give error

Shutting down query evaluator.
Interpreting results.
A fatal error occurred: Could not process query metadata.
Error was: No query kind specified(NO_KIND_SPECIFIED).

I find a solution, i get check @id and @kind. I see all file .ql in Security folder and they exists.
Can anyone help me!

@max-schaefer suggests this is because some queries in the ql/javascript/ql/src/Security directory have unusual values of @kind that the results interpretation process does not support.

In any case, the error message is confusing and misleading -- it should at least indicate which query it is complaining about.

@dbartol, do you have an immediate feeling for which code is involved here?
@hmakholm hmakholm added the bug label Mar 5, 2020
@max-schaefer
Copy link

@max-schaefer max-schaefer commented Mar 6, 2020

some queries in the ql/javascript/ql/src/Security directory

For example this one: https://github.com/Semmle/ql/blob/master/javascript/ql/src/Security/Summaries/ExtractFlowStepSummaries.ql
@adityasharad adityasharad added the CLI label Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CLI bug
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@adityasharad @hmakholm @max-schaefer
You can’t perform that action at this time.