GitHub Copilot fails with managedSettings.resolve network fetch error on Windows
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 12/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Stack tecnologico
- javascript, vscode
Direzione di ricerca
Start with the stack trace, which points to managedSettings.resolve in @github/copilot-sdk/dist/client.js, and check how that call reaches https://api.github.com/copilot_internal/user. The reporter's curl.exe output shows SEC_E_UNTRUSTED_ROOT, so the cause may be the Windows certificate store or a TLS-inspection proxy rather than the code. Done means the root cause is confirmed, or the logs needed to confirm it are listed on the issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Environment
GitHub Copilot is not working in Visual Studio Code. When attempting to use Copilot, the following error occurs:
Error: Request managedSettings.resolve failed with message:
network fetch failed: request failed: error sending request for url
https://api.github.com/copilot_internal/user
The error originates from the GitHub Copilot SDK within VS Code and prevents the request from completing.
Environment
Operating System: Windows
Editor: Visual Studio Code
Feature: GitHub Copilot / Copilot Chat
Network connectivity: TCP connection to api.github.com:443 succeeds.
TLS verification: Windows curl.exe reports SEC_E_UNTRUSTED_ROOT when accessing the GitHub API.
Steps to Reproduce
Launch Visual Studio Code on Windows.
Open GitHub Copilot or Copilot Chat.
Attempt to initiate a Copilot request.
Observe the network fetch error.
Expected Behavior
GitHub Copilot should successfully connect to the GitHub API, retrieve the required user or managed settings, and allow Copilot features to function normally.
Actual Behavior
The request to https://api.github.com/copilot_internal/user fails with a network fetch error. Copilot cannot complete the operation.
The error stack references the following components:
vscode-jsonrpc connection handling
@github/copilot-sdk/dist/client.js
managedSettings.resolve
Additional Diagnostics
The following command confirms that the destination is reachable over TCP:
Test-NetConnection api.github.com -Port 443
Result:
TcpTestSucceeded : True
However, this request fails during TLS certificate validation:
curl.exe -v https://api.github.com/copilot_internal/user
Reported error:
schannel: SEC_E_UNTRUSTED_ROOT (0x80090325)
The certificate chain was issued by an authority that is not trusted.
The certificate displayed in Chrome for *.github.com identifies Sectigo Public Server Authentication CA DV E36 as the issuer.
Investigation Requested
Please investigate whether this failure is related to TLS certificate-chain validation, the Copilot SDK's network handling, or a regression in the VS Code Copilot integration.
Please advise which diagnostic logs or additional information are needed to identify the root cause.
Note: The available diagnostics suggest a certificate-trust issue, but the underlying cause has not yet been confirmed.
How to Reproduce
Install and launch Visual Studio Code on Windows.
Install or update the GitHub Copilot and GitHub Copilot Chat extensions.
Sign in to GitHub with an account that has Copilot access.
Open Copilot Chat and attempt to start a conversation or execute a Copilot request.
Observe the error related to managedSettings.resolve and the request to https://api.github.com/copilot_internal/user.
Expected behavior
GitHub Copilot should successfully establish a secure connection to the required GitHub API endpoints, retrieve the necessary user and managed settings, and initialize the Copilot session without network errors. Copilot Chat and other enabled Copilot features should work normally.
Screenshots & Logs
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 19
- Fork
- 8
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/github-copilot-appmod
-
[Bug]:Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 15/100
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
-
[Bug]:Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 10/100
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 15/100
-
bug
Difficoltà 3/5 Mezza giornata Idoneità per principianti 55/100
Tutte le issue di microsoft/github-copilot-appmod
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
rajbos/ai-engineering-fluency#2490 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
area:holodeck review-finding
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
hyperdrive-technology/holodeck#196 ·
I maintainer di solito rispondono entro 1 giorno
-
c:pytools c:testsystem
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
eclipse-sumo/sumo#18384 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno