Voice mode dowload fails with corporate proxy ENOTFOUND
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Descripción
### 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_
Guía de contribución
Línea de trabajo
Comienza por vendored foundry-local-sdk/script/install-utils.cjs e inspecciona la solución alternativa adjunta apply-foundry-proxy-patch.js; después reproduce la descarga de /voice usando el entorno de proxy indicado. Se considera terminado cuando el paquete Microsoft.AI.Foundry.Local.Core se descarga correctamente a través del proxy corporativo configurado sin depender de NODE_OPTIONS.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- node.js
- Área
- networking
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bien especificado
- Aptitud para principiantes
- 48/100