PowerShell / PowerShell/vscode-powershell

CI Tests: PowerShellEditorServices build cannot restore .NET reference packs (NuGet feed returns 401), failing every branch since 2026-06-25

Aperta Adatta ai principianti
#5,592 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Lingua principale
TypeScript
Stelle
1.9k
Fork
548
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

CI Tests has failed on every branch since 2026-06-25, including main (the last successful run was 2026-06-25). It fails in the Build, test and package step while building the sibling PowerShellEditorServices checkout, before any of this repository's own tests run:

error : Failed to download package 'Microsoft.NETCore.App.Ref.8.0.31' from 'https://pkgs.dev.azure.com/powershell/.../nuget/v3/flat2/microsoft.netcore.app.ref/8.0.31/microsoft.netcore.app.ref.8.0.31.nupkg'.
error : Response status code does not indicate success: 401 (Unauthorized - No local versions of package 'microsoft.netcore.app.ref'; please provide authentication to access versions from upstream that have not yet been saved to your feed.)

PowerShellEditorServices/nuget.config clears all sources and only lists https://pkgs.dev.azure.com/powershell/PowerShell/_packaging/powershell/nuget/v3/index.json. That feed's index.json is public (HTTP 200), but package downloads return 401 to anonymous clients, for both the name-based and GUID-based URLs, e.g. microsoft.netcore.app.ref 8.0.19 and 8.0.31. The same package is publicly downloadable from nuget.org (HTTP 302). Since ci-test.yml checks out PSES's default branch and builds it, public GitHub runners can no longer restore these .NET reference packs.

Effect: no PR can get a green CI Tests run; several PRs (e.g. #5558) are stuck on this.

Workaround that unblocks a run — add nuget.org to the sources after checking out PSES (see the temporary commit in #5558):

- name: Add nuget.org to the PowerShellEditorServices sources
  shell: pwsh
  run: |
    # keep the PowerShell feed, add nuget.org as a fallback for the ref packs

With it, the build succeeds and the extension's tests actually execute (the remaining macOS failure in that run was the unrelated, flaky VS Code Insiders download: spawn ... Electron ENOENT).

Suggested fixes (maintainer's call):

  1. Add nuget.org to PowerShellEditorServices/nuget.config, or enable anonymous upstream access on the feed.
  2. Check out a pinned PSES tag in ci-test.yml rather than its default branch.

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia con ci-test.yml e il PowerShellEditorServices/nuget.config sottoposto a checkout; traccia il modo in cui il passaggio Build, test and package ripristina i pacchetti di riferimento .NET. Applica la correzione di source o checkout approvata dai maintainer, quindi esegui nuovamente CI Tests e conferma che i test dell’estensione vengano eseguiti con un ripristino riuscito.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
github-actions, powershell, yaml
Ambito
build-system, ci-cd
Tipo di issue
Bug
Difficoltà
2/5
Tempo stimato
1-3 ore
Stato di attività
Attiva
Chiarezza
Specificata chiaramente
Idoneità per principianti
78/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.