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

Inconsistent behaviour when switching from Dev Container to WSL folder (reopen in WSL) #10596

Open
SimonCahill opened this issue Dec 27, 2024 · 0 comments
Assignees
Labels
containers Issue in vscode-remote containers

Comments

@SimonCahill
Copy link

As stated in the title, there is some inconsistent behaviour when switching between dev containers and WSL in my current version of VS Code (Code is Insiders branch).

Version info:

Version: 1.97.0-insider (user setup)
Commit: 89f808979a5151 bd91324e65d4f7ab1 b62896983
Date: (1 wk ago)
Electron: 322.6
ElectronBuildld: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
128.37438-electron.o
OS: Windows_NTx64 10.02635

// DevContainers
Identifier   ms-vscode-remote.remote-containers
Version      0.395.0
Last Updated 2024-12-11, 21:07:09

// WSL
Identifier   ms-vscode-remote.remote-wsl
Version      0.88.5
Last Updated 2024-11-07, 15:20:37

When hitting F1 and entering "Reopen in WSL", the following menu shows up:

Image

hitting the suggested menu item causes an error message to display:
Image

while producing the following logs:

2024-12-27 14:07:41.071 [error] TypeError: Cannot read properties of undefined (reading 'env')
	at Object.getEnv (c:\Users\simon\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.88.5\dist\node\extension.js:2:247350)
	at c:\Users\simon\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.88.5\dist\node\extension.js:2:267631
	at async t.getWSLExecServer (c:\Users\simon\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.88.5\dist\node\extension.js:2:267610)
	at async t.AuthorityResourceStore.get (c:\Users\simon\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.88.5\dist\node\extension.js:2:210477)
	at async c:\Users\simon\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.88.5\dist\node\extension.js:2:223145
	at async fw.h (file:///c:/Users/simon/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:115:32825) remote-wsl.reopenInWSL {"value":"ms-vscode-remote.remote-wsl","_lower":"ms-vscode-remote.remote-wsl"}

If, however, I use the Remote menu at the bottom-left of the window, the VS Code behaves as expected and reopens the folder "locally" (in WSL).

Image

Image

Note: Although I didn't explicitely show this in screenshots, using F1 and explicitly hitting Dev Containers: Reopen... works as expected. This is an issue in the WSL remote extension.

@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants