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

Failed to install wasm-experimental workload with error "Source array was not long enough" after installing .NET 10.0 SDK #45632

Closed
EmilyFeng97 opened this issue Dec 26, 2024 · 4 comments · Fixed by #46653
Assignees
Labels
Area-Workloads release blocking untriaged Request triage from a team member

Comments

@EmilyFeng97
Copy link

EmilyFeng97 commented Dec 26, 2024

Describe the bug

Failed to install wasm-experimental workload.
Image

C:\Users\v-xxxx>dotnet workload install wasm-experimental

Skipping NuGet package signature verification.
Skipping NuGet package signature verification.
Downloading Microsoft.NET.Runtime.WebAssembly.Templates.net10.Msi.x64 (10.0.0-alpha.1.24625.1)
Workload installation failed. Rolling back installed packs...
Workload installation failed: Source array was not long enough. Check the source index, length, and the array's lower bounds. (Parameter 'sourceArray')

To Reproduce

  1. Install .NET 10.0 Preview 1 SDK from github and add feed
  2. Install wasm-experimental workload with below command:
    dotnet workload install wasm-experimental

Note

  1. This issue does not repro when installing only Dev 17.13 Preview 3(including 9.0.x sdk)
  2. This issue does not repro if I run the command prompt as administrator
  3. This issue also repro when install the wasm-tools or maui workload

Expected

The workload can be installed successfully.

Further technical details

  • Include the output of dotnet --info
.NET SDK:
 Version:           10.0.100-alpha.1.24623.6
 Commit:            6fbcb37c6f
 Workload version:  10.0.100-manifests.6327884e
 MSBuild version:   17.14.0-preview-24620-02+a71903d96

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\10.0.100-alpha.1.24623.6\

.NET workloads installed:
There are no installed workloads to display.
Configured to use loose manifests when installing new manifests.

Host:
  Version:      10.0.0-alpha.1.24620.10
  Architecture: x64
  Commit:       57ab984bd0

.NET SDKs installed:
  10.0.100-alpha.1.24623.6 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 10.0.0-alpha.2.24623.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 10.0.0-alpha.1.24620.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 10.0.0-alpha.1.24622.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download
@vdanche
Copy link
Member

vdanche commented Feb 5, 2025

Also happens when installing maui workload in CLI using net10.0.100-preview.1.25104.3
Image

@EmilyFeng97
Copy link
Author

Verify this issue on the coherent build of .NET 10.0 Preview 1, it still repro when installing wasm-experimental and wasm-tools workloads.
SDK Version: 10.0.100-preview.1.25103.13
Runtimes Version: 10.0.0-preview.1.25080.5

@vdanche
Copy link
Member

vdanche commented Feb 12, 2025

not repro on 10.0.100-preview.1.25110.2 SDK

Image

@Forgind
Copy link
Member

Forgind commented Feb 12, 2025

Thanks for confirming @vdanche!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Workloads release blocking untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants