Open smowton opened 3 years ago
After one failure, it is possible to produce more by running other queries against the same database, always ending with - - - COMPILATION DONE - - -
. Selecting a different database fixes the problem, but then switching back to the original continues to yield this message.
Restarting VSCode allows querying the database.
What was the quick query you ran, on what database? And is this problem reproducible? I just briefly tried to run a quick query myself and could not reproduce.
The No result from server
means that the query server closed the query without ever sending any results back. I'm not entirely sure what situations this occurs in.
It doesn't seem to matter what the query is, and the database is a trivial test DB consisting only of a single Test.java file and a skeleton pom.xml.
Possibly important: the previous DB before a reboot is often under /tmp
and so not present after rebooting (simply rm -r
'ing it doesn't seem to be enough to reproduce the fault, though)
Steps I took:
codeql database create --language=java db
in cwd /tmp/x
/tmp/x/db
Result: No result from server
. Once this has happened to one database, I have never yet been able to get it to happen to any other database without an intervening reboot.
Describe the bug
Received message
no result from server
on running a quick query.Immediately preceding extension log:
Query server log:
Version CLI v2.5.5 Extension v1.5.1 VSCode v1.57.1 Platform: OSX Big Sur (11.4)