GitHub Copilot fails with managedSettings.resolve network fetch error on Windows
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 12/100
- Issue-Typ
- Bug
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- javascript, vscode
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 19
- Forks
- 8
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus microsoft/github-copilot-appmod
-
[Bug]:Offenbug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 15/100
-
bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 48/100
-
[Bug]:Offenbug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 10/100
-
bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 15/100
-
bug
Schwierigkeit 3/5 Ein halber Tag Anfängerfreundlichkeit 55/100
Alle Issues in microsoft/github-copilot-appmod
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
SublimeText/AdvancedNewFile#211 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
taskcluster/taskcluster#9284 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
`[daemons]` fails to resolve standalone file tasks by their display name (`runs unknown task`)Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
area:devenv origin:agent type:bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
overengineeringstudio/effect-utils#1949 ·
Maintainer antworten meist innerhalb von 1 Tag