Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NETSDKE2E] [Regression]With 8.0.100-rc.1.23414.11 installed, the RID shows incorrectly on Linux Alpine3.18 Arm64 #34627

Closed
v-xiaofchen opened this issue Aug 15, 2023 · 5 comments
Labels
Area-CLI untriaged Request triage from a team member

Comments

@v-xiaofchen
Copy link

Environment:

Alpine3.18 Arm64 in docker
.NET 8.0.100-rc.1.23414.11(runtime-8.0.0-rc.1.23414.4)

To Reproduce

Repro steps:

  1. Prepare Alpine3.18 Arm64 in docker

  2. Extract dotnet-sdk-8.0.100-rc.1.23414.11-linux-musl-arm64.tar.gz, and use the export command to set DOTNET_ROOT to the extracted folder's location and then ensure .NET is in PATH

  3. Run 'dotnet --info' and observe

Expected behavior

RID shows "alpine.3.18-arm64".

Actual behavior

RID shows "linux-musl-arm64"
alpinearm641

Regression?

This issue not repro on 8.0.100-rc.1.23407.2(runtime- 8.0.0-rc.1.23381.3)
alpinearm642

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-CLI untriaged Request triage from a team member labels Aug 15, 2023
@v-xiaofchen v-xiaofchen changed the title [NETSDKE2E] [Regression]With 8.0.100-rc.1.23414.11 installed,the RID shows abnormally on Linux Alpine3.18 Arm64 [NETSDKE2E] [Regression]With 8.0.100-rc.1.23414.11 installed,the RID shows incorrect on Linux Alpine3.18 Arm64 Aug 15, 2023
@v-xiaofchen v-xiaofchen changed the title [NETSDKE2E] [Regression]With 8.0.100-rc.1.23414.11 installed,the RID shows incorrect on Linux Alpine3.18 Arm64 [NETSDKE2E] [Regression]With 8.0.100-rc.1.23414.11 installed, the RID shows incorrectly on Linux Alpine3.18 Arm64 Aug 15, 2023
@martincostello
Copy link
Member

martincostello commented Aug 15, 2023

I've noticed a similar issue just now with Windows too.

The RID has changed from win10-x64 to win-x64.

This is then causing dotnet publish --self-contained --runtime win10-x64 to fail with this error (logs):

Error: /usr/share/dotnet/sdk/8.0.100-rc.1.23414.11/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5): error NETSDK1083: The specified RuntimeIdentifier 'win10-x64' is not recognized.

8.0.100-rc.1.23412.1

❯ dotnet --info
.NET SDK:
 Version:   8.0.100-rc.1.23412.1
 Commit:    e9e2e45de3

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Coding\martincostello\website\.dotnetcli\sdk\8.0.100-rc.1.23412.1\

8.0.100-rc.1.23414.11

❯ dotnet --info
.NET SDK:
 Version:   8.0.100-rc.1.23414.11
 Commit:    1c0b692a4e

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Coding\martincostello\api\.dotnet\sdk\8.0.100-rc.1.23414.11\

@marcpopMSFT
Copy link
Member

@dsplaisted @elinor-fung is this fallout of the simplified ridgraph changes? @v-xiaofchen @martincostello Does seting UseRidGraph to true fix this?

See this for more details:
#34279

@martincostello
Copy link
Member

I wasn't sure if this was an intentional change or not (I did do a quick Google search for something but I didn't find anything). I realise that ingesting daily builds means that I'm probably getting intentional things before they're officially communicated to users.

If this is intended and the end-result behaviour is the same, then I can update my testing branch to publish for win-x64 instead.

@kasperk81
Copy link
Contributor

not a fallout

use simple rids or set UseRidGraph=true for old behavior

@dsplaisted
Copy link
Member

Yes, this is an expected result of the RID graph changes.

@marcpopMSFT marcpopMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-CLI untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

5 participants