microsoft / microsoft/vscode-remote-release

Workspace folder being deleted when session left up over the weekend.

Open
#10,907 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ssh
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Is there an existing issue for this bug?
  • I have searched the existing open issues and found none that apply.
  • If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
  • I have read and performed the troubleshooting steps
  • I have tried both values of the remote.SSH.useLocalServer setting
  • My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
  • I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I COULD successfully SSH to the remote machine with the generated SSH command

Remote-SSH Log
Remote-SSH Log 

[09:20:41.384] Log Level: 2
[09:20:41.412] VS Code version: 1.99.1
[09:20:41.412] Remote-SSH version: remote-ssh@0.119.0
[09:20:41.413] linux x64
[09:20:41.415] SSH Resolver called for "ssh-remote+10.0.1.2", attempt 1
[09:20:41.418] remote.SSH.useLocalServer = true
[09:20:41.419] remote.SSH.useExecServer = true
[09:20:41.419] remote.SSH.bindHost = {}
[09:20:41.419] remote.SSH.path = undefined
[09:20:41.419] remote.SSH.configFile = undefined
[09:20:41.419] remote.SSH.useFlock = true
[09:20:41.419] remote.SSH.lockfilesInTmp = false
[09:20:41.420] remote.SSH.localServerDownload = auto
[09:20:41.420] remote.SSH.remoteServerListenOnSocket = false
[09:20:41.420] remote.SSH.defaultExtensions = []
[09:20:41.420] remote.SSH.defaultExtensionsIfInstalledLocally = []
[09:20:41.420] remote.SSH.loglevel = 2
[09:20:41.420] remote.SSH.enableDynamicForwarding = true
[09:20:41.421] remote.SSH.enableRemoteCommand = false
[09:20:41.421] remote.SSH.serverPickPortsFromRange = {}
[09:20:41.421] remote.SSH.serverInstallPath = {}
[09:20:41.421] remote.SSH.permitPtyAllocation = false
[09:20:41.421] remote.SSH.preferredLocalPortRange = undefined
[09:20:41.421] remote.SSH.useCurlAndWgetConfigurationFiles = false
[09:20:41.422] remote.SSH.experimental.chat = false
[09:20:41.422] remote.SSH.experimental.enhancedSessionLogs = false
[09:20:41.422] remote.SSH.httpProxy = {}
[09:20:41.422] remote.SSH.httpsProxy = {}
[09:20:41.438] SSH Resolver called for host: 10.0.1.2
[09:20:41.438] Setting up SSH remote "10.0.1.2"
[09:20:41.444] Acquiring local install lock: /tmp/vscode-remote-ssh-433a827b-install.lock
[09:20:41.447] Looking for existing server data file at /home/alex/.config/Code/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-433a827b-7c6fdfb0b8f2f675eb0b47f3d95eeca78962565b-0.119.0-es/data.json
[09:20:41.447] Found existing data file
[09:20:41.447] Found local server running: {"remoteListeningOn":{"port":32909},"osReleaseId":"debian","arch":"x86_64","sshAuthSock":"","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"ef1204cc-e784-478a-8ed7-157469108e5c","pid":438188,"ipcHandlePath":"/run/user/1000/vscode-ssh-askpass-07be1fd6f79760dee80056ef6e3fd3921680f9dd.sock","socksPort":36567,"startupTime":1745241568324}
[09:20:41.456] Found running server - short-circuiting install
[09:20:41.458] Starting forwarding server. local port 44783 -> socksPort 36567 -> remotePort 32909
[09:20:41.459] Forwarding server listening on port 44783
[09:20:41.459] Waiting for ssh tunnel to be ready
[09:20:41.460] [Forwarding server port 44783] Got connection 0
[09:20:41.461] Tunneled port 32909 to local port 44783
[09:20:41.461] Resolved "ssh-remote+10.0.1.2" to "port 44783"
[09:20:41.469] Initizing new exec server for ssh-remote+10.0.1.2
[09:20:41.470] Resolving exec server at port 44783
[09:20:41.471] [Forwarding server port 44783] Got connection 1
[09:20:41.543] Exec server for ssh-remote+10.0.1.2 created and cached
[09:20:41.543] Extensions to install: 
[09:20:41.550] ------




[09:20:41.550] No hints found in the recent session.
[09:20:41.623] [server] Checking /home/alex/.vscode-server/cli/servers/Stable-7c6fdfb0b8f2f675eb0b47f3d95eeca78962565b/log.txt and /home/alex/.vscode-server/cli/servers/Stable-7c6fdfb0b8f2f675eb0b47f3d95eeca78962565b/pid.txt for a running server...
[09:20:41.624] [server] Found running server (pid=178738)
[09:20:42.470] Opening exec server for ssh-remote+10.0.1.2
[09:20:42.473] Verified and reusing cached exec server for ssh-remote+10.0.1.2
[09:20:42.474] No hints found in the recent session.
[09:20:42.477] Opening exec server for ssh-remote+10.0.1.2
[09:20:42.479] Verified and reusing cached exec server for ssh-remote+10.0.1.2
[09:20:42.480] No hints found in the recent session.

Expected Behavior

I expect to not have my workspace randomly deleted.

Actual Behavior

The directory containing my workspace was deleted.

Steps To Reproduce
  1. Remote SSH to a server.
  2. Leave the session running over a weekend, with no changes to either end of the machine.
Anything else?

This appears to be the same behavior from #7517, only my session was never closed.

This has now happened twice, both between the same machines and both on the same project.

The remote machine is a virtual machine running on the same computer as the local machine. There was no change to the configuration of either machine; as I noted, it was just left running over the weekend. No other directories have been affected.

Most of the troubleshooting steps listed above are completely not applicable to this situation.

I honestly don't know how else to troubleshoot this.

I opened a new session after re-cloning my repository, so I don't actually have the logs from when it happened. I will attempt to reproduce it to pull the relevant logs. . .With a copy that I don't have active work in.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing this report with issue #7517 and reproduce the weekend-long Remote-SSH session using a copy without active work. Capture the Remote-SSH log when the workspace directory is deleted, then trace the session and workspace lifecycle involved. Done means identifying the deletion trigger and preventing unintended workspace removal.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.