dotnet / install-scripts

MIT License
133 stars 72 forks source link

vscode_intstallingdotnetruntimeerror #380

Closed Muhamed4 closed 1 year ago

Muhamed4 commented 1 year ago

Repro steps:

1.

Extension Version: 1.0.0 Error Message: .NET Acquisition Failed: Installation failed: Error: Command failed: "/home/anonymous/.vscode/extensions/ms-dotnettools.vscode-dotnet-runtime-1.7.0/dist/install scripts/dotnet-install.sh" -InstallDir "/home/anonymous/.config/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/7.0.10" -Version 7.0.10 -Runtime dotnet

gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dotnet_install: Error: Extraction failed

Error Stack: Error: .NET Acquisition Failed: Installation failed: Error: Command failed: "/home/anonymous/.vscode/extensions/ms-dotnettools.vscode-dotnet-runtime-1.7.0/dist/install scripts/dotnet-install.sh" -InstallDir "/home/anonymous/.config/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/7.0.10" -Version 7.0.10 -Runtime dotnet

gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dotnet_install: Error: Extraction failed

at /home/anonymous/.vscode/extensions/vscode-dotnet-runtime-library/dist/Acquisition/DotnetCoreAcquisitionWorker.js:90:27
donJoseLuis commented 1 year ago

@YuliiaKovalova Please note this is impacting our friends in the vscode.

donJoseLuis commented 1 year ago

@Muhamed4 greetings. I am sorry you are experiencing this. We have had a couple of similar issues from your team recently; thus far, the root-cause has been networking for each instance.

Please consider collecting a network trace when you experience such download failures. We have monitoring that successfully download the scripts & bits, twice per hour. The network trace will quickly identify if CLI blob is serving the bits.

donJoseLuis commented 1 year ago

@Muhamed4

We are unable to reproduce as we expected. There is something interesting about your network which is the root-cause of the problems.

We strongly encourage you get network traces of...

  1. vscode download of bits via install scripts
  2. stand alone install scripts getting bits from CLI blob storage

I think the above steps will quickly show you somewhere in your network is the culprit.

MicrosoftTeams-image (1)