microsoft / microsoft/vscode-remote-release

"Connect in current window" button in remote explorer opening folders in new window

Open
#11,562 1 comment 1 reaction 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 did not try step 2 of the troubleshooting steps

Remote-SSH Log
Remote-SSH Log

[10:50:54.990] Log Level: 2
[10:50:55.068] VS Code version: 1.113.0
[10:50:55.071] Remote-SSH version: remote-ssh@0.122.0
[10:50:55.073] win32 x64
[10:50:55.097] SSH Resolver called for "ssh-remote+vm", attempt 1
[10:50:55.147] remote.SSH.useLocalServer = false
[10:50:55.150] remote.SSH.useExecServer = true
[10:50:55.153] remote.SSH.bindHost = {}
[10:50:55.155] remote.SSH.showLoginTerminal = false
[10:50:55.157] remote.SSH.remotePlatform = {"vm":"linux","10.189.72.139":"linux","10.22.184.135":"linux","10.189.72.241":"linux","10.189.72.206":"linux","10.189.73.56":"linux","10.189.72.226":"linux","10.189.64.121":"linux","10.189.73.76":"linux","10.189.64.222":"linux","10.189.72.152":"linux","10.21.118.241":"linux","10.189.73.30":"linux"}
[10:50:55.161] remote.SSH.path = C:\WINDOWS\System32\OpenSSH\ssh.exe
[10:50:55.163] remote.SSH.configFile = 
[10:50:55.165] remote.SSH.useFlock = true
[10:50:55.167] remote.SSH.lockfilesInTmp = false
[10:50:55.169] remote.SSH.localServerDownload = always
[10:50:55.171] remote.SSH.remoteServerListenOnSocket = true
[10:50:55.173] remote.SSH.defaultExtensions = []
[10:50:55.174] remote.SSH.defaultExtensionsIfInstalledLocally = []
[10:50:55.177] remote.SSH.loglevel = 2
[10:50:55.180] remote.SSH.enableDynamicForwarding = true
[10:50:55.185] remote.SSH.enableRemoteCommand = false
[10:50:55.189] remote.SSH.serverPickPortsFromRange = {}
[10:50:55.191] remote.SSH.serverInstallPath = {}
[10:50:55.193] remote.SSH.permitPtyAllocation = false
[10:50:55.194] remote.SSH.preferredLocalPortRange = undefined
[10:50:55.196] remote.SSH.useCurlAndWgetConfigurationFiles = true
[10:50:55.197] remote.SSH.experimental.chat = true
[10:50:55.199] remote.SSH.experimental.enhancedSessionLogs = false
[10:50:55.200] remote.SSH.httpProxy = {"*":"http://proxy-in.its.hpecorp.net:8080"}
[10:50:55.202] remote.SSH.httpsProxy = {"*":"http://proxy-in.its.hpecorp.net:443"}
[10:50:55.266] SSH Resolver called for host: vm
[10:50:55.269] Setting up SSH remote "vm"
[10:50:55.310] Using commit id "cfbea10c5ffb233ea9177d34726e6056e89913dc" and quality "stable" for server
[10:50:55.313] Extensions to install: 
[10:50:55.348] Install and start server if needed
[10:50:55.364] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[10:50:55.530] > OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2

[10:50:55.550] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 4300 vm sh
[10:50:55.556] Generated SSH command: 'type "C:\Users\scariaj\AppData\Local\Temp\vscode-linux-multi-line-command-vm-395091911.sh" | "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 4300 vm sh'
[10:50:55.562] Using connect timeout of 17 seconds
[10:50:55.566] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[10:50:55.938] > 
[10:50:55.941] Got some output, clearing connection timeout
[10:50:55.947] > 
[10:51:01.594] > 3299552af215: running
> Script executing under PID: 2005539
[10:51:01.610] > Found existing installation at /root/.vscode-server...
[10:51:01.823] > Starting VS Code CLI...
[10:51:01.840] > Removing old logfile at /root/.vscode-server/.cli.cfbea10c5ffb233ea9177d34726e6056e89913dc.log
> Spawned remote CLI: 2005704
> Waiting for server log...
[10:51:01.870] > Waiting for server log...
[10:51:01.915] > 3299552af215: start
> listeningOn==/tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f==
> osReleaseId==ubuntu==
> arch==x86_64==
> vscodeArch==x64==
> bitness==64==
> tmpDir==/run/user/0==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> serverStartTime==89==
> execServerToken==111a1aa1-1a11-1aa1-1111-1aa11a1111a1==
> platformDownloadPath==cli-alpine-x64==
> SSH_AUTH_SOCK====
> DISPLAY====
> 3299552af215: end
[10:51:01.917] Received install output: 
listeningOn==/tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f==
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/0==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==89==
execServerToken==111a1aa1-1a11-1aa1-1111-1aa11a1111a1==
platformDownloadPath==cli-alpine-x64==
SSH_AUTH_SOCK====
DISPLAY====

[10:51:01.919] Remote server is listening on socket /tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f
[10:51:01.920] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"socketPath":"/tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f"},"osReleaseId":"ubuntu","arch":"x86_64","sshAuthSock":"","display":"","tmpDir":"/run/user/0","platform":"linux","execServerToken":"111a1aa1-1a11-1aa1-1111-1aa11a1111a1"},"serverStartTime":89,"installUnpackCode":""}
[10:51:01.933] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -L 127.0.0.1:4362:/tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f vm sh
[10:51:01.936] Spawning tunnel with: type "C:\Users\scariaj\AppData\Local\Temp\vscode-linux-multi-line-command-vm-98594209.sh" | "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -L 127.0.0.1:4362:/tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f vm sh
[10:51:01.938] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[10:51:02.211] > 
[10:51:02.226] > 
[10:51:07.861] > 
> -e Connected to SSH Host - Please do not close this terminal
[10:51:07.863] Spawned SSH tunnel between local port 4362 and remote target socket /tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f
[10:51:07.864] Waiting for ssh tunnel to be ready
[10:51:07.867] Tunneled socket /tmp/code-5721db20-f786-4d7f-885e-840f1d6a737f to local port 4362
[10:51:07.869] Resolved "ssh-remote+vm" to "port 4362"
[10:51:07.882] Initizing new exec server for ssh-remote+vm
[10:51:07.884] Resolving exec server at port 4362
[10:51:09.351] Exec server for ssh-remote+vm created and cached
[10:51:09.355] Extensions to install: 
[10:51:09.378] ------




[10:51:09.380] Enhanced session logs are disabled.
[10:51:09.884] [server] Checking /root/.vscode-server/cli/servers/Stable-cfbea10c5ffb233ea9177d34726e6056e89913dc/log.txt and /root/.vscode-server/cli/servers/Stable-cfbea10c5ffb233ea9177d34726e6056e89913dc/pid.txt for a running server...
[10:51:09.886] [server] Found running server (pid=2003047)

Expected Behavior

Previously opened folders should open in current window when pressing the button

Actual Behavior

Previously opened folders open in new window

Steps To Reproduce
  1. open a folder on remote
  2. close it and open another folder on remote
  3. 1st folder will pop up as one of the recently opened folders in remote explorer
  4. click on "connect in current window" or "->" button on the folder
Anything else?

No response

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

Reproduce the issue using the four steps in the report, focusing on the Remote Explorer's previously opened folders and the "connect in current window" action. Done means selecting that action reopens the previously opened folder in the current window rather than a new window; no source file or test is named in the report.

Written by the indexing model from the issue text.

Assessment

Domain
desktop-dev, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.