github / github/codeql-cli-binaries

show error message NO_KIND_SPECIFIED

Offen
#67 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
CLI
Vorherrschende Sprache
Keine Sprachdaten
Sterne
1k
Forks
184
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

i use codeql database analyze .\demo2 ..\vscode-codeql-starter\ql\javascript\ql\src\code_test.ql --format=csv --output=a/js-results.csv, but a error happen

```
E:\code analysis\test2> codeql database analyze .\demo2 ..\vscode-codeql-starter\ql\javascript\ql\src\code_test.ql --format=csv --output=a/js-results.csv
Running queries.
Compiling query plan for E:\code analysis\vscode-codeql-starter\ql\javascript\ql\src\code_test.ql.
[1/1 comp 10.1s] Compiled E:\code analysis\vscode-codeql-starter\ql\javascript\ql\src\code_test.ql.
Starting evaluation of codeql-javascript\code_test.ql.
[1/1 eval 474ms] Evaluation done; writing results to codeql-javascript\code_test.bqrs.
Shutting down query evaluator.
Interpreting results.
A fatal error occurred: Could not process query metadata for E:\code analysis\vscode-codeql-starter\ql\javascript\ql\src\code_test.ql.
Error was: No query kind specified [NO_KIND_SPECIFIED]

```
code_test.ql:
```
import javascript
from DataFlow::CallNode call
where call.getCalleeName() = "open"
select call
```
The analysis code is as follows:

[test.md](https://github.com/github/codeql-cli-binaries/files/6564874/test.md)

I have already specified the ql file,but this is still an error...
Can someone help me.....
I really appreciate this!

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Reproduce the command against code_test.ql using the example in test.md, then inspect how the CLI processes metadata for that query. Check the query's metadata requirements and the CodeQL CLI handling of missing query kind information. Done means the command completes without NO_KIND_SPECIFIED and produces the requested CSV results.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript
Bereich
devtools, security
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.