Voice mode dowload fails with corporate proxy ENOTFOUND
- Lingua principale
- Shell
- Stelle
- 11.2k
- Fork
- 1.9k
- Merge medio
- 14h 16m
- PR unite (30g)
- 6
Descrizione
### Describe the bug
[apply-foundry-proxy-patch.js](https://github.com/user-attachments/files/29883462/apply-foundry-proxy-patch.js)
The download of the voice mode inference runtime failed with "Error: Failed to download Microsoft.AI.Foundry.Local.Core 1.2.3 from any configured feed (api.nuget.org, pkgs.dev.azure.com): getaddrinfo ENOTFOUND pkgs.dev.azure.com" behind the corporate proxy despite proper setup of Px and env vars.
Root cause: the vendored `foundry-local-sdk/script/install-utils.cjs` downloads NuGet packages using a bare `https.get()` call. Node's built-in `http`/`https` modules never read HTTP_PROXY/HTTPS_PROXY env vars on their own (unlike curl or most other tools), so the request bypasses the proxy entirely and fails to resolve DNS/connect directly.
Additionally, `copilot.exe` is a compiled Node "Single Executable Application" (SEA) binary that silently ignores NODE_OPTIONS, so the usual `-r some-proxy-shim.js` / `global-agent` tricks do NOT work here — the shim never loads inside the actual copilot process or its worker threads.
See attached file for temporary workaround.
### Affected version
GitHub Copilot CLI 1.0.70
### Steps to reproduce the behavior
Enter /voice on
Confirm download of model
Observe download failure
### Expected behavior
Setup behind corporate proxy is supported.
### Additional context
_No response_
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con vendored foundry-local-sdk/script/install-utils.cjs ed esamina il workaround apply-foundry-proxy-patch.js allegato, quindi riproduci il download di /voice utilizzando l’ambiente proxy indicato. Il lavoro è completato quando il pacchetto Microsoft.AI.Foundry.Local.Core viene scaricato correttamente tramite il proxy aziendale configurato senza dipendere da NODE_OPTIONS.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- node.js
- Ambito
- networking
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 48/100