-
Notifications
You must be signed in to change notification settings - Fork 202
Timeout during query compilation should produce failed query history item #250
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
Comments
The behaviour you are describing isn't exactly what I'm seeing. The query does seem to be added to the query history page as an error. Though, the message is incorrect. I'm seeing something like:
It looks like the cli is incorrectly tagging the query as being cancelled instead of timedout. |
Is it possible that the incorrect tag is because the timeout is on vscode's side, not the cli? And when the timeout is reached, vscode triggers the cancel in the cli? |
Oddly though, when I actually try to cancel the query, the result comes out as |
Now, I'm able to reproduce the error described by @henrymercer. Looks like if I cancel during the compilation phase, I see the behaviour described above. If I cancel during the run phase, then I see the behaviour that I described, |
This change converts a cancelled query into a synthetic query result that is displayed in query history. Also includes some light refactoring. Closes github#250.
This change converts a cancelled query into a synthetic query result that is displayed in query history. Also includes some light refactoring. Closes github#250.
Describe the bug
When query compilation times out, the message
The request (id: 6, method: 'compilation/compileQuery') has been cancelled
is added to the extension log, but a query history item corresponding to the timed out query is not added to the query history view.To Reproduce
codeQL.runningQueries.timeout
to 1 secondExpected behavior
The query history view should contain an item corresponding to the timed-out compilation with a failed icon and the status "timed out".
The text was updated successfully, but these errors were encountered: