You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Short description: sometimes, the SSH extension gets into a locked state when launching VS Code. There are apparently locks in the server installation which never disappear. Fortunately, a quick workaround is to simply close VS Code and rm the locks from a standard terminal SSH into the server installation folder. However, when launching the SSH VS Code afterward the workspace appears to be blank quite often
.
VSCode Version: 1.43 Insiders
OS Version: MacOS 10.15.3
Steps to Reproduce:
Have a SSH session in VS Code that doesn't manage to connect
Remove manually the locks in the server installation folder
Relaunch VS Code SSH session and notice the workspace is blank.
(4). (Workaround) Relaunch again VS Code
Does this issue occur when all extensions are disabled?: No
The text was updated successfully, but these errors were encountered:
Short description: sometimes, the SSH extension gets into a locked state when launching VS Code. There are apparently locks in the server installation which never disappear. Fortunately, a quick workaround is to simply close VS Code and rm the locks from a standard terminal SSH into the server installation folder. However, when launching the SSH VS Code afterward the workspace appears to be blank quite often
.
Steps to Reproduce:
(4). (Workaround) Relaunch again VS Code
Does this issue occur when all extensions are disabled?: No
The text was updated successfully, but these errors were encountered: