microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.62k stars 279 forks source link

Stucked at Downloading with wget #9562

Closed AmitRDesai closed 6 months ago

AmitRDesai commented 7 months ago

Type: Bug

After update it stucked at "Downloading with wget"

Extension version: 0.108.0 VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z) OS version: Windows_NT x64 10.0.22631 Modes: Connection to 'ssh-remote+dev-box' could not be established

bamurtaugh commented 7 months ago

Could you please provide some more details, such as:

Thanks!

jjyyxx commented 7 months ago

@bamurtaugh I'm also faced with this timeout, so I tested the URL manually. After some test, I doubt that vscode.download.prss.microsoft.com have broken connectivity in certain part of the world.

Accessing https://update.code.visualstudio.com/commit:903b1e9d8990623e3d7da1df3d33db3e42d80eda/server-linux-x64/stable redirects me to https://vscode.download.prss.microsoft.com/dbazure/download/stable/903b1e9d8990623e3d7da1df3d33db3e42d80eda/vscode-server-linux-x64.tar.gz.

However, this domain vscode.download.prss.microsoft.com (resolved to 182.254.60.101) cannot be connected to in China mainland, but a test via Google Colab seems OK (resolved to 152.199.39.108).

yilinc515 commented 7 months ago

@bamurtaugh I'm also faced with this timeout, so I tested the URL manually. After some test, I doubt that vscode.download.prss.microsoft.com have broken connectivity in certain part of the world.

Accessing https://update.code.visualstudio.com/commit:903b1e9d8990623e3d7da1df3d33db3e42d80eda/server-linux-x64/stable redirects me to https://vscode.download.prss.microsoft.com/dbazure/download/stable/903b1e9d8990623e3d7da1df3d33db3e42d80eda/vscode-server-linux-x64.tar.gz.

However, this domain vscode.download.prss.microsoft.com (resolved to 182.254.60.101) cannot be connected to in China mainland, but a test via Google Colab seems OK (resolved to 152.199.39.108).

confirming this issue still exists, domain vscode.download.prss.microsoft.com is down with Error 504 `[16:21:34.971] > wget download failed

https://vscode.download.prss.microsoft.com/dbazure/download/stable/8b3775030ed1a69b13e4f4c628c612102e30a681/vscode_cli_alpine_x64_cli.tar.gz: 2024-02-23 16:21:34 ERROR 504: Gateway Timeout.`

yilinc515 commented 7 months ago

Update: wget from vscode.download.prss.microsoft.com for vscode-cli-8b3775030ed1a69b13e4f4c628c612102e30a681.tar.gz is now working. However, running the downloaded executable causes a segmentation fault on the remote server (distro: Linux 3.10.0-1160.105.1.el7.x86_64 x86_64). [username@sh02-ln04 ~/.vscode-server]$ /home/users/username/.vscode-server/code-8b3775030ed1a69b13e4f4c628c612102e30a681 Segmentation fault

jjyyxx commented 7 months ago

@roblourens In addition, I am very confused that even if I managed to setup a working local proxy, make the "Downloading VS Code server locally" fallback successful and start coding, the next time (possibly the next day) I connect the remote server, the torture starts again, by trying to download a server with exactly the same hash Installing to /home/fedora/.vscodeserver/bin/903b1e9d8990623e3d7da1df3d33db3e42. The current status is, instead of a one-time pain, it takes around 5 minutes every day for each remote host I need to connect 😭

roblourens commented 6 months ago

However, this domain vscode.download.prss.microsoft.com (resolved to 182.254.60.101) cannot be connected to in China mainland, but a test via Google Colab seems OK (resolved to 152.199.39.108).

Is everyone having this problem from the China mainland?

jjyyxx commented 6 months ago

@roblourens Thanks for your attention. For me, everything worked again after the 1.87.0 release. I'm not sure if it is attributed to the new release or the network connection, though. (Most likely to be a network issue)

But aside from the hopefully temporary issue, the code path of local download fallback seems very broken to me, leading to at least three distinct failure patterns (imagine that remote wget failed, but local download succeeded, and scp to remote finished):

  1. The Remote SSH log just stuck at installing;
  2. The Remote SSH log complains that another installation is in progess repeatedly and indefinitely (happens when I close a window in state 1);
  3. Even after killing some remote process, clearing file locks, making it finally work for the current session, after a certain period of time (maybe 1 day), Remote SSH tries to start the download procedure again.

All the above are confusing and annoying UX that I experienced in the last few days. Since it works again now, I could not provide further confirmation or the steps to reproduce. But I wish that someone could review this less used code path to ensure it really works.

roblourens commented 6 months ago

The orignal PRSS issue actually should be fixed now https://github.com/microsoft/vscode/issues/205938#issuecomment-1960995706

WIth the locking issue, you can manually delete the lock file to clear it up, but also setting "remote.SSH.useExecServer": true (soon to become default) may also resolve it.

VSCodeTriageBot commented 6 months ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

yusyel commented 6 months ago

@roblourens checking ""remote.SSH.useExecServer" did not solve my issue.

code -v : 1.87.2 863d2581ecda6849923a2118d93a088b0745d9d6 x64

ssh add on:Version: 0.109.0