VS Code

Visual Studio (VS) Code is a multi-platform source-code editor developed by Microsoft. It can be used with a variety of programming languages and can have its base functionality extended through extensions available via its marketplace. The base editor itself is free, but some extensions may require paid subscriptions.

There are also forks/open source alternatives of VS Code, such as Cursor or VSCodium. The same general principals below apply to these editors as well.

Cluster Usage

It can be convenient when using our SLURM computing clusters to open a connection to a VS Code Server session on the submission node(s) that you have access to via VS Code's Remote - SSH extension. Steps to set this up can be found here. Use your UMIACS username and the fully qualified domain name (FQDN) of the submission node you want to connect to. Password authentication does not provide an option to save your password, so for convenience, you may want to set up an SSH key.

For a list of active issues with the Remote - SSH extension, please see Microsoft's GitHub tracker here.

Best Practices

Because of the multi-tenant nature of our submission nodes, using the Remote - SSH extension to connect to a VS Code Server running on a submission node can have adverse affects on other users simultaneously using the submission nodes if not properly managed. The following is a list of "best practices" that we ask you please follow to minimize the chance of impacting others on submission nodes. We have compiled the list through observation as well as through discussion with users.

Use only as a code editor

VS Code can perform many common file management operations, such as moving, copying, or deleting files or directories. However, the overhead of providing progress updates / status messages through VS Code's UI can cause load spikes that result in other processes on the submission node (both system-level and other users') slowing down. This is especially the case if operating on thousands to millions of small image or video files. In extreme cases, it can seem as though the submission node is wholly unresponsive.

The best way to combat this is to use VS Code as just a code editor as strictly as you can (meaning creating new and/or editing existing source code files only). Use standard command-line programs such as mv/cp/rm in VS Code's terminal window or a separate application's terminal window for local file management instead, or use the techniques advertised here for larger data transfers between nodes.

Do not open large files

Files that you open in VS Code's text editor on a remote machine through the Remote - SSH extension are loaded entirely into RAM on the remote machine. Because of the persistence of VS Code Server processes, opening several unique files may result in them all remaining in RAM for extended periods of time even if you no longer have tabs open for them in the Tab Bar.

As such, please refrain from opening large files (more than a few MB) in VS Code itself on submission nodes. Use a lighter-weight command-line based text editor such as vim or otherwise in VS Code's terminal window or a separate application's terminal window for local file editing instead.

If you absolutely need to open one or more large files for a very brief period of time on a submission node, please clean up your server session on that node (see below section) as soon as possible when done.

Clean up when done

If you are done using VS Code for an extended period of time (several hours / overnight), consider manually killing your server session on the submission node when exiting. By default, VS Code Server will keep the processes used by your session active for a few hours after you disconnect, keeping the VS Code Server processes on the submission node you were using alive, despite no longer actively being used.

This can be done by opening the Command Palette (Ctrl+Shift+P) and searching "Kill VS Code Server on Host...".

Select the submission node you were using and click on it.

Wait a few seconds and you should get a message confirming the command went through.

The next time you connect to the same submission node, you will have a fresh VS Code session on it.

Common Issues

If you are having trouble SSH'ing to a submission node with VS Code, check if your home directory is full.

1. Connect to one of your Nexus submission nodes via SSH not using VS Code.
2. Navigate to your home directory.

   cd ~

3. Check if it is full.

   df -h .

4. If it is full (Avail 0), delete some files to free up at least ~100MB of space.

   Filesystem                                    Size  Used Avail Use% Mounted on
   data.isilon.umiacs.umd.edu:/ifs/umiacs/homes   30G   30G     0 100% /fs/nfshomes

5. Try connecting with VS Code again.