-
Notifications
You must be signed in to change notification settings - Fork 188
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
When I connect to Codespace, CodeQL get installed, each time #3560
Comments
Hi @Sim4n6 , thanks for raising an issue. Are you seeing the CodeQL CLI get installed every time you connect to a pre-existing Codespace, or just when you create a new one? For new Codespaces we have to download the CLI to install it since it is stored in the Codespace storage. |
Pré existing one. |
Thanks for clarifying. One more question, do you have the CodeQL extension installed globally or do you use VS Code Settings sync, syncing your extensions and settings to all Codespaces? |
Hi @Sim4n6! Another few questions to help us look into this! Are you seeing this in all codespaces, or is it specific to just a single repository? And could you share the |
I will do that tonight |
I've got something interesting the followinfg error message
And it starts installing CodeQL each time I fire VSCode on Windows (latest stable release) and click on connect to Codespace (via down left corner remote btn) Select a running Codespace 'NAME'. Content of .devcontainer/devcontainer.json file: {
"extensions": [
"rust-lang.rust-analyzer",
"bungcip.better-toml",
"github.vscode-codeql",
"hbenl.vscode-test-explorer",
"ms-vscode.test-adapter-converter",
"slevesque.vscode-zipexplorer"
],
"settings": {
"files.watcherExclude": {
"**/target/**": true
},
"codeQL.runningQueries.memory": 2048
}
}
I hope I answered your questions, pleasE? |
Settings === @ext:GitHub.vscode-codeql ... This is the root cause. |
@Sim4n6 👋 hello! I am trying to reproduce the issue. I was wondering if you could share if the CLI executable path you screenshotted above was set in the When I try to reproduce in either of those locations, on creation of the codespace I get the same log message you pasted above and CodeQL is installed. When I stop and reconnect to the codespace, however, instead of getting the installation again, I get a Also, could you share which version of the CodeQL CLI extension you're using, and which version of the Codespaces extension? Thank you! |
Here is the content of settings.json on {
"git.autofetch": true,
"codeQL.telemetry.enableTelemetry": false,
"codeQL.cli.executablePath": "/home/sim4n6/CodeQL-Home/codeql-cli/codeql", # this is the problematic one
"workbench.colorTheme": "Quiet Light",
"window.zoomLevel": 1,
"remote.SSH.remotePlatform": {
"143.x.x.x": "linux"
},
"githubPullRequests.pullBranch": "never",
"github.copilot.advanced": {
}
} I also have a Linux local setup where the user's home is
and
I think something is different right away. I started getting |
I believe you released some fix right ? because the WARNING that was showing up at #3560 (comment) is different, I'm getting this error this time:
|
wait, it does happen occasionally when the VSCode ext is reloaded ... |
the issue persists please feel free to ask me further questions ... |
I was able to reproduce this. I wonder if we need to add |
OK...so I'm not crazy. Looks like this is a bug in vscode. See microsoft/vscode#210363. If you feel like it, you can comment on it just to let the team know that there are others affected by it. |
Much bromance sent from this part of the globe 🌐 |
microsoft/vscode#210363 is now fixed. The fix will go to vscode insiders edition first and then into a general release. I don't know when this will be, but it may not be until August that it is generally available (I'm not familiar with the vscode release cycle). |
Perfect. |
It is simple on my side.
Each time I fire a codespace on my local Vscode editor, it starts a codeql installation even though the codeql was not updated or asked to ?
The question now is why ? what should be done ? how to omit that?
The text was updated successfully, but these errors were encountered: