Voice mode dowload fails with corporate proxy ENOTFOUND
- Vorherrschende Sprache
- Shell
- Sterne
- 11.2k
- Forks
- 1.9k
- Ø Merge
- 14 Std. 16 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
### 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_
Beitragsleitfaden
Rechercherichtung
Beginne mit vendored foundry-local-sdk/script/install-utils.cjs und untersuche die angehängte Umgehungslösung apply-foundry-proxy-patch.js. Reproduziere anschließend den /voice-Download unter Verwendung der gemeldeten Proxy-Umgebung. Als erledigt gilt, wenn das Paket Microsoft.AI.Foundry.Local.Core über den konfigurierten Unternehmensproxy erfolgreich heruntergeladen wird, ohne auf NODE_OPTIONS angewiesen zu sein.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- node.js
- Bereich
- networking
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 48/100