Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dotnet-install from 2.1.3xx channel tries to download nonexistent 2.1.301-preview-008906 rather than 2.1.301

See original GitHub issue

Steps to reproduce

.\dotnet-install.ps1 -Channel release/2.1.3xx

Expected behavior

Downloads and installs the 2.1.301 build, or some later daily build.

Actual behavior

#> .\dotnet-install.ps1 -Channel release/2.1.3xx
dotnet-install: Downloading link: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301-preview-008906/dotnet-sdk-2.1.301-preview-008906-win-x64.zip
dotnet-install: Cannot download: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301-preview-008906/dotnet-sdk-2.1.301-preview-008906-win-x64.zip
dotnet-install: Downloading legacy link: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301-preview-008906/dotnet-dev-win-x64.2.1.301-preview-008906.zip
Exception calling "Invoke" with "0" argument(s): "Failed to download https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301-preview-008906/dotnet-dev-win-x64.2.1.301-preview-008906.zip.
StatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
...

This file determines the latest version on this channel, and it points to the 2.1.301-preview-008906 build which doesn’t exist: https://dotnetcli.blob.core.windows.net/dotnet/Sdk/release/2.1.3xx/latest.version

ProdCon did produce artifacts that have that prerelease version in the blob feed:

https://github.com/dotnet/versions/blob/7a833dddfddc27f2074b755b94234a25b9757637/build-info/dotnet/product/cli/release/2.1/build.xml#L607

Some files in the Sdk/2.1.301 blob storage dir point to that virtual dir having some association to the 2.1.301-preview-008906 prerelease (they certainly should be related, since we expect the ProdCon build to be the one that’s published!):

https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.1.301/VS.Redist.Common.Net.Core.SDK.MSBuildExtensions.2.1.301-preview-008906.nupkg https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.1.301/VS.Redist.Common.Net.Core.SDK.x64.2.1.301-preview-008906.nupkg https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.1.301/VS.Redist.Common.Net.Core.SDK.x86.2.1.301-preview-008906.nupkg

My guess is the artifacts were copied to Sdk/2.1.301 and (mostly) renamed because this is a stable build, but the channel’s latest.version wasn’t updated to match. The solution might be as simple as fixing the latest.version files.

Issue Analytics

State:
Created 5 years ago
Comments:12 (12 by maintainers)

Top GitHub Comments

1reaction

johnbeisnercommented, Jul 31, 2018

Successfully tested: dotnet-install.ps1 -Channel release/2.1.3xx

dotnet-install: Downloading link: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301/dotnet-sdk-2.1.301-win-x64.zip dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.301/dotnet-sdk-2.1.301-win-x64.zip

1reaction

johnbeisnercommented, Jul 31, 2018

Assertion: 2.1.301-preview-008906 is the same as 2.1.301 Why: The commit id in the release/2.1.3xx ‘latest.version’ pointer file for 2.1.301-preview-008906 is identical to the commit id for the CLI release tag for 2.1.301: https://github.com/dotnet/cli/releases/tag/v2.1.301 59524873d628a6b0156fd84b2e8a632418fe83f1

I will update the ‘latest.version’ and ‘latest.coherent.version’ to point at: “2.1.301”

Top Results From Across the Web

Discussion Milestone

dotnet-install from 2.1.3xx channel tries to download nonexistent 2.1.301-preview-008906 rather than 2.1.301. #9519 by dagood was closed on Jan 31, 2020.