cc_staff
290
edits
Visual Studio Code: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Cedar now at Alma 9) |
No edit summary |
||
| Line 122: | Line 122: | ||
|content= | |content= | ||
The newest versions of [https://code.visualstudio.com/docs/remote/linux#_remote-host-container-wsl-linux-prerequisites VS Code Server no longer support CentOS 7], which affects connections to <b>Graham</b> and <b>Niagara</b>. Users can update their version of VS Code to 1.86.1 or later in order to connect, but will see warnings about the unsupported operating system. | The newest versions of [https://code.visualstudio.com/docs/remote/linux#_remote-host-container-wsl-linux-prerequisites VS Code Server no longer support CentOS 7], which affects connections to <b>Graham</b> and <b>Niagara</b>. Users can update their version of VS Code to 1.86.1 or later in order to connect, but will see warnings about the unsupported operating system. | ||
}} | |||
<!--T:24--> | <!--T:24--> | ||
* Note: an older version of VS Code still works through [[JupyterHub#VS_Code|JupyterHub]]. | * Note: an older version of VS Code still works through [[JupyterHub#VS_Code|JupyterHub]]. | ||
<!--T:25--> | <!--T:25--> | ||
| Line 133: | Line 133: | ||
* Connect to all login nodes and stop (with <code>kill <PID></code>) all VS Code processes you see in the output of <code>ps aux | grep $USER</code> or <code>top -u $USER</code>. | * Connect to all login nodes and stop (with <code>kill <PID></code>) all VS Code processes you see in the output of <code>ps aux | grep $USER</code> or <code>top -u $USER</code>. | ||
* If the above does not fix the problem, carefully delete the content of the <code>~/.vscode-server</code> directory, and then reconnect for a fresh installation of VS Code Server. | * If the above does not fix the problem, carefully delete the content of the <code>~/.vscode-server</code> directory, and then reconnect for a fresh installation of VS Code Server. | ||
<!--T:27--> | |||
* We recently determined that in the last week of August/2024 a bug with the Remote-SSH extension for VSCode was introduced. As far as we could ascertain, scp is not working as expected. That is not our software, this is a Microsoft product, so we offer best effort support. | |||
Here is some more info on the bug: | |||
https://github.com/microsoft/vscode-remote-release/issues/10174#issuecomment-2316629187 | |||
Here is a suggestion of a workaround using wget: | |||
https://github.com/microsoft/vscode-remote-release/issues/10174#issuecomment-2316093550 | |||
Add "remote.SSH.useCurlAndWgetConfigurationFiles: true" to Remote-SSH settings. | |||
And here is another suggestion using the "Remote Tunnels" extension. | |||
You can run code tunnel (google vscode cli and download it) and use github or microsoft account (oauth) and connect to a remote vscode server, here a niagara login node. You can have all the "benefits" of not using mfa as long as your server is running: | |||
https://code.visualstudio.com/docs/remote/tunnels | |||
=See also= <!--T:16--> | =See also= <!--T:16--> | ||