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
Under some specific circumstance(s) the model editor gets into an infinite loading state, with no error message about what has gone wrong.
Version
The CodeQL and VS Code version in which the bug occurs.
To reproduce
There are 2 scenarios where I have observed this. In scenario 1 , I admit that I am aware of the fact that the database has a missing file, and then perhaps this behaviour makes sense? (though I still think it would be hard to debug without an error message). In scenario 2, I do not know what the underlying issue is.
Expected behavior
I expect a failure message to display so that the reasons for the hang can be fixed (ie if there is something wrong with a database then how would a user know that unless there is some error message). I am not currently sure why I cannot model the database in the example as a dependency...
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Something similar is happening to me, the extension logs only say:
Failed to load results: Internal error.
Error: Internal error.
at handleResponse (/Users/tony/.vscode/extensions/github.vscode-codeql-1.13.1/out/extension.js:36803:40)
at handleMessage (/Users/tony/.vscode/extensions/github.vscode-codeql-1.13.1/out/extension.js:36613:11)
at processMessageQueue (/Users/tony/.vscode/extensions/github.vscode-codeql-1.13.1/out/extension.js:36628:13)
at Immediate.<anonymous> (/Users/tony/.vscode/extensions/github.vscode-codeql-1.13.1/out/extension.js:36604:11)
at processImmediate (node:internal/timers:478:21)
Describe the bug
Under some specific circumstance(s) the model editor gets into an infinite loading state, with no error message about what has gone wrong.
Version
The CodeQL and VS Code version in which the bug occurs.
VSCode CodeQL Extension version - v1.13.1
CodeQL CLI versions tested with: 2.16.3, 2.17.1, 2.17.4, 2.17.5
To reproduce
There are 2 scenarios where I have observed this. In scenario 1 , I admit that I am aware of the fact that the database has a missing file, and then perhaps this behaviour makes sense? (though I still think it would be hard to debug without an error message). In scenario 2, I do not know what the underlying issue is.
Both scenarios use the sample Java app in this repo
Scenario 1)
successfully creates a database with no SampleInner.java file (probably this causes the silent error?)
end of CodeQL Query Server log shows:
CodeQL Extension log tail:
Scenario 2)
successfully creates a database with both, as expected, Sample.java and SampleInner.java file
end of CodeQL Query Server log shows:
CodeQL Extension log tail:
both yield a infinite Modelling Java panel like:
Expected behavior
I expect a failure message to display so that the reasons for the hang can be fixed (ie if there is something wrong with a database then how would a user know that unless there is some error message). I am not currently sure why I cannot model the database in the example as a dependency...
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: