GitHub Copilot fails with managedSettings.resolve network fetch error on Windows
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 12/100
- Tipo de issue
- Bug
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Ativa
- Stack de tecnologia
- javascript, vscode
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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
- Linguagem predominante
- Sem dados de linguagem
- Estrelas
- 19
- Forks
- 8
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de microsoft/github-copilot-appmod
-
[Bug]:Abertabug
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 15/100
-
bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 48/100
-
[Bug]:Abertabug
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 10/100
-
bug
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 15/100
-
bug
Dificuldade 3/5 Meio dia Facilidade para iniciantes 55/100
Todas as issues de microsoft/github-copilot-appmod
Issues semelhantes
-
freshness freshness:verdict-moving
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
thoroc/context-radar#279 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 1 dia
-
area: tests difficulty: easy enhancement good first issue hacktoberfest help wanted
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
tdk-landscape/tdk-import#35 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 78/100