-
Notifications
You must be signed in to change notification settings - Fork 200
Unable to view source code files in a CodeQL database over SSH remote session #872
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
Thanks for reporting. We are aware that the extension does not work well when used with the remote ssh extension. When we fix these issues, we will be sure that your use case is working as well. |
Hmm, is there a way we could disable the I tried to see if I could add this myself, but not sure how to do it when the UI button is referenced here in a JSON file (instead of TypeScript): vscode-codeql/extensions/ql-vscode/package.json Lines 315 to 322 in f856e3a
|
That code snippet is the declaration of the command. The command is bound to an action in this code: vscode-codeql/extensions/ql-vscode/src/databases-ui.ts Lines 275 to 283 in 7eb12e0
If you wanted to change behaviour depending on the workspace kind, you would wrap the code above in some sort of if statement. |
Describe the bug
When connecting from VSCode (Linux) to a remote Linux server over SSH, it is not possible to view the source files contained in a CodeQL database. This includes browsing the archive in the Explorer, and also following links in CodeQL results. An error such as the following will be shown:
Version
CodeQL extension version: 1.4.8
CodeQL CLI version: 2.4.6
Platform: linux x64
Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T16:45:26.313Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Linux x64 5.8.0-53-generic
To reproduce
Expected behavior
The source file should be opened.
Additional context
This works correctly when working locally on both Linux hosts. It's only when working over SSH remotely that I have experienced this.
The text was updated successfully, but these errors were encountered: