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
It appears when the download of the CodeQL CLI fails, e.g. due to network issues, the extension just gets stuck. No error dialog is shown and nothing is logged.
Have not tested whether this affects other download actions as well, such as downloading databases from LGTM.com.
Open the CodeQL CLI download folder; on Windows %appdata%\Code\User\globalStorage\github.vscode-codeql
Delete or rename the distribution folder
Start VSCode
Run the command >CodeQL: Check for CLI Updates
While the download is in progress disconnect from the internet
❌ The progress gets stuck; nothing happens
Expected behavior
As soon as a download failure occurs the extension should inform the user, and permit restarting the download (currently not possible because current download is not properly cancelled on failure).
Additional context
Maybe error handling also has to be improved; the documentation for pipe says that the destination has to be closed manually on error; it looks like this is currently not done.
The text was updated successfully, but these errors were encountered:
Describe the bug
It appears when the download of the CodeQL CLI fails, e.g. due to network issues, the extension just gets stuck. No error dialog is shown and nothing is logged.
Have not tested whether this affects other download actions as well, such as downloading databases from LGTM.com.
Version
Extension:
VSCode:
To reproduce
%appdata%\Code\User\globalStorage\github.vscode-codeql
>CodeQL: Check for CLI Updates
❌ The progress gets stuck; nothing happens
Expected behavior
As soon as a download failure occurs the extension should inform the user, and permit restarting the download (currently not possible because current download is not properly cancelled on failure).
Additional context
Maybe error handling also has to be improved; the documentation for
pipe
says that the destination has to be closed manually on error; it looks like this is currently not done.The text was updated successfully, but these errors were encountered: