Vscode-remote-release: VSC Insiders unable to connect to WSL server

[afernando79]

Issue Type: Bug

Start VSC Insiders (within Windows)
Open folder
Bottom left Reopen folder in WSL

Results:
[2019-12-04 10:09:04.286] Resolving wsl+ubuntu, resolveAttempt: 1
[2019-12-04 10:09:05.324] Starting VS Code Server inside WSL (u)
[2019-12-04 10:09:05.324] Extension version: 0.41.2, Windows build: 18362. Multi distro support: available. WSL path support: enabled
[2019-12-04 10:09:06.308] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d u -e sh -c "[ -d ~/.vscode-server-insiders/bin/] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2019-12-04 10:09:08.338] Unable to detect if server is already installed: Error: Command failed: C:\WINDOWS\System32\wsl.exe -d u -e sh -c "[ -d ~/.vscode-server-insiders/bin/ ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2019-12-04 10:09:08.339] Launching C:\WINDOWS\System32\wsl.exe -d u sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" insider .vscode-server-insiders 0 ' in c:\Users\andrew.fernando.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.41.2
[2019-12-04 10:09:09.701] There is no distribution with the supplied name.
[2019-12-04 10:09:09.701]
[2019-12-04 10:09:09.703] VS Code Server for WSL closed unexpectedly.
[2019-12-04 10:09:09.703] For help with startup problems, go to
[2019-12-04 10:09:09.704] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tip

It appears the name of the distribution is being truncated to "u" instead of "ubuntu". Running 'C:\WINDOWS\System32\wsl.exe -d u -e sh -c "[ -d ~/.vscode-server-insiders/bin/] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"' fails with above error even from a command prompt.

Running 'C:\WINDOWS\System32\wsl.exe -d ubuntu -e sh -c "[ -d ~/.vscode-server-insiders/bin/] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"' is successful.

Could this be some sort of indexing the first character of the string instead of an array (assuming it would expect to get a list of distributions from which it would select the first).

VS Code version: Code - Insiders 1.41.0-insider (97855786a014be2440751b038b373c3726e11fe8, 2019-12-03T05:40:39.806Z)
OS version: Windows_NT x64 10.0.18362
Fetching remote diagnostics for 'WSL: Ubuntu' failed: VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz (8 x 1992)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.73GB (3.86GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

Fetching remote diagnostics for 'WSL: Ubuntu' failed: VS Code Server for WSL closed unexpectedly.
Check WSL terminal for more details.

Extensions: none

[laem]

I can confirm, I have the same issue today.

[tomasaschan]

So do I, but on a different version: VS Code version: Code - Insiders 1.41.0-insider (7f1975a, 2019-12-04T10:20:42.228Z).

[SferaDev]

Same issue on version 1.41.0-insider (7f1975a, 2019-12-04T10:20:42.228Z).

[JacerOmri]

same on 1.41.0-insider, i'm adding the console log here, the only difference i spotted is the truncated "U", on my log it's uppercase. I don't know if that helps with anything.

[2019-12-04 14:22:31.979] Resolving wsl+Ubuntu, resolveAttempt: 1
[2019-12-04 14:22:32.052] Starting VS Code Server inside WSL (U)
[2019-12-04 14:22:32.052] Extension version: 0.41.2, Windows build: 19025. Multi distro support: available. WSL path support: enabled
[2019-12-04 14:22:32.199] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d U -e sh -c "[ -d ~/.vscode-server-insiders/bin/7f1975a4fb29d0a788c21f17eb2aad056fec22d8 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2019-12-04 14:22:32.265] Unable to detect if server is already installed: Error: Command failed: C:\WINDOWS\System32\wsl.exe -d U -e sh -c "[ -d ~/.vscode-server-insiders/bin/7f1975a4fb29d0a788c21f17eb2aad056fec22d8 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2019-12-04 14:22:32.265] Launching C:\WINDOWS\System32\wsl.exe -d U sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 7f1975a4fb29d0a788c21f17eb2aad056fec22d8 insider .vscode-server-insiders 0  ' in c:\Users\xxxx\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.41.2
[2019-12-04 14:22:32.302] There is no distribution with the supplied name.
[2019-12-04 14:22:32.302] 
[2019-12-04 14:22:32.303] VS Code Server for WSL closed unexpectedly.
[2019-12-04 14:22:32.303] For help with startup problems, go to
[2019-12-04 14:22:32.303] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips

[JacerOmri]

just updated the Remote - WSL extension nad it's working fine now

[afernando79]

Hi @JacerOmri ,
What do we need to do to resolve the issue? Wait for the next build or is there a fix I can apply while I wait?

[tomasaschan]

@afernando79 Updating the extension was enough to get it working on my machine as well.

It would be _very_ helpful if updating VS Code to a version that's incompatible with the current installed Remote - WSL version would update the extension automatically. Barring that, at least surfacing this possibility in the error message would probably unblock a lot of people (this isn't the first time I've had to update the extension manually after it was broken by an update to VS Code).

[aeschli]

This was a bug in the extension, not related to an update of VSCode. Sorry for the trouble.
Extensions are tested for updates every 12h, unless you open the extensions viewlet.
I agree that for this case polling more often would be ideal.

Duplicate of https://github.com/microsoft/vscode-remote-release/issues/1962

[envp]

This is still occurring on:

Version: 1.41.1 (system setup)
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.19041

[aeschli]

@envp Please file a new issue with the full content of the WSL log.