Skip to content
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

Blank workspace #92161

Closed
sebastienwood opened this issue Mar 6, 2020 · 1 comment
Closed

Blank workspace #92161

sebastienwood opened this issue Mar 6, 2020 · 1 comment
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@sebastienwood
Copy link

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
Capture d’écran, le 2020-03-06 à 09 20 31
.

  • VSCode Version: 1.43 Insiders
  • OS Version: MacOS 10.15.3

Steps to Reproduce:

  1. Have a SSH session in VS Code that doesn't manage to connect
  2. Remove manually the locks in the server installation folder
  3. 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

@roblourens
Copy link
Member

It sounds like this is the same as microsoft/vscode-remote-release#2518

@roblourens roblourens added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 17, 2020
@github-actions github-actions bot locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants