cc_staff
782
edits
Visual Studio Code: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
(CentOS 7 issue) |
(Marked this version for translation) |
||
| Line 90: | Line 90: | ||
VS Code Terminal in which you may be prompted for your 2nd factor of authentication. | VS Code Terminal in which you may be prompted for your 2nd factor of authentication. | ||
=Closing your connection= | =Closing your connection= <!--T:19--> | ||
<!--T:20--> | |||
When closing the local VS Code window, the remote process of VS Code Server may keep running in background, which tends to accumulate orphan processes on that login node. Not only that, but your next connection may connect to a different login node, which can cause issues and confusion. '''To cleanly close a connection, click on the bottom-left corner of VS Code and select ''Close Remote Connection'' on top of the window.''' | When closing the local VS Code window, the remote process of VS Code Server may keep running in background, which tends to accumulate orphan processes on that login node. Not only that, but your next connection may connect to a different login node, which can cause issues and confusion. '''To cleanly close a connection, click on the bottom-left corner of VS Code and select ''Close Remote Connection'' on top of the window.''' | ||
| Line 107: | Line 108: | ||
### If you get prompted for the type of operating system, select <b>Linux</b> | ### If you get prompted for the type of operating system, select <b>Linux</b> | ||
=Troubleshooting= | =Troubleshooting= <!--T:21--> | ||
==The remote session does not work anymore== | ==The remote session does not work anymore== <!--T:22--> | ||
<!--T:23--> | |||
{{Warning | {{Warning | ||
|title=As of February 1st, 2024 | |title=As of February 1st, 2024 | ||
| Line 116: | Line 118: | ||
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>Béluga</b>, <b>Cedar</b>, <b>Graham</b> and <b>Niagara</b>. Users are invited to develop on their local computer and upload their code manually to the cluster. | 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>Béluga</b>, <b>Cedar</b>, <b>Graham</b> and <b>Niagara</b>. Users are invited to develop on their local computer and upload their code manually to the cluster. | ||
<!--T:24--> | |||
* Note 1: Béluga will get upgraded in the upcoming months. | * Note 1: Béluga will get upgraded in the upcoming months. | ||
* Note 2: an older version of VS Code still works through [[JupyterHub#VS_Code|JupyterHub]]. | * Note 2: an older version of VS Code still works through [[JupyterHub#VS_Code|JupyterHub]]. | ||
}} | }} | ||
<!--T:25--> | |||
Because VS Code is intended for a different use case than developing on our clusters, having several instances of VS Code Server running on different login nodes can lead to issues. To fix them: | Because VS Code is intended for a different use case than developing on our clusters, having several instances of VS Code Server running on different login nodes can lead to issues. To fix them: | ||
<!--T:26--> | |||
* 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. | ||