SSH remote install doesn't notice that remote system ran out of disk space

[virtuald]

Here are relevant snippets of the 1-Remote -SSH.log file:

[13:59:09.150] > Linux 5.4.0-125-generic #141~18.04.1-Ubuntu SMP Thu Aug 11 20:15:56 UTC 2022
[13:59:09.151] Platform: linux
[13:59:09.215] > /bin/bash
[13:59:09.215] Shell: bash
[13:59:09.215] Creating bash subshell inside "bash"
[13:59:09.278] > bash version:  4.4.20(1)-release
[13:59:09.294] > bash version:  4.4.20(1)-release
[13:59:09.335] > 81859fcc697d: running
[13:59:09.402] > Acquiring lock on /home/<user>/.vscode-server/bin/74b1f979648cc44d385a2286793c226e611f59e7/vscode-remote-lock.<user>.74b1f979648cc44d385a2286793c226e611f59e7
[13:59:09.412] > Installing to /home/<user>/.vscode-server/bin/74b1f979648cc44d385a2286793c226e611f59e7...
[13:59:09.419] > 81859fcc697d%%1%%
[13:59:09.431] > Downloading with wget
[13:59:11.086] > wget download failed

[13:59:23.456] Copying file to remote with scp

[13:59:54.958] > scp: /home/<user>/.vscode-server/bin/74b1f979648cc44d385a2286793c226e611f59e7/vscode-server.tar.gz: No space left on device

[13:59:56.042] stderr> tar: vscode-server-linux-x64/product.json: Wrote only 7168 of 7274 bytes
[13:59:57.395] stderr> tar: vscode-server-linux-x64/node_modules/@vscode/ripgrep/bin/rg: Wrote only 2048 of 10240 bytes
[13:59:57.417] stderr> tar: vscode-server-linux-x64/node_modules/@vscode/ripgrep/SECURITY.md: Cannot write
[13:59:57.418] stderr> : No space left on device

These last messages repeat quite a bit.

After failing to install, the installer tries again instead of giving up or telling the user that they ran out of space.

[eleanorjboyd]

Hello! Our logs should output an error on the lines follow [13:59:11.086] > wget download failed , could you send over those lines? I am curious if wget produces a useful error which explains this disk issue we could parse and respond to. Otherwise we can use the scp error value and try and resolve this bug by returning the disk issue back to the user faster. Thanks!

[github-actions[bot]]

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!