Describe the bug
I got an "Internal error. (codeQL.codeLensQuickEval)" error dialog in vscode.
Version
CodeQL extension version: 1.5.9
CodeQL CLI version: 2.7.2
Platform: darwin x64
Vs code:
Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:37:28.172Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.4.0
To reproduce
The way to reproduce it for me is:
open TaintedPathCustomizations.qll, line 452 (in the blocks predicate).
Remove .getBaseString().
Quick evaluate the predicate.
Expected behavior
A graceful error.
Additional context
When this modification is present in the code base, unrelated queries will also fail. This might make it quite hard to find the root cause of the problem in some instances.
But this is not blocking me at all, I just thought that someone might find it valuable to be made aware.
This part of the output seems relevant:
SEVERE: Internal error: com.semmle.util.exception.CatastrophicError: Ambiguous super dispatch: method Node.asExpr() can be reached through extends and instanceof supertypes.
java.util.concurrent.CompletionException: com.semmle.util.exception.CatastrophicError: Ambiguous super dispatch: method Node.asExpr() can be reached through extends and instanceof supertypes.
The text was updated successfully, but these errors were encountered:
Thank you for logging this error. I think we need some better error handling around invalid quick queries. At the very least, better error messages would be helpful.
Describe the bug
I got an "Internal error. (codeQL.codeLensQuickEval)" error dialog in vscode.
Version
CodeQL extension version: 1.5.9
CodeQL CLI version: 2.7.2
Platform: darwin x64
Vs code:
Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:37:28.172Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.4.0
To reproduce
The way to reproduce it for me is:
blocks
predicate)..getBaseString()
.Expected behavior
A graceful error.
Additional context
When this modification is present in the code base, unrelated queries will also fail. This might make it quite hard to find the root cause of the problem in some instances.
But this is not blocking me at all, I just thought that someone might find it valuable to be made aware.
This part of the output seems relevant:
The text was updated successfully, but these errors were encountered: