Keeps hanging: TypeError: fetch failed at node:internal/deps/undici/undici:13392:13 #3357
Comments
github-actions
bot
added
the
triage-needed
|
Can you do F1 -> GitHub Copilot Chat Diagnostics and attach that output |
bhavyaus
added
~info-needed
|
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue. Happy Coding! |
|
@etmoore I was having the same problem. Based on this thread, https://github.com/orgs/community/discussions/147055#discussioncomment-11606773, I updated WSL to 2.3.26 (Latest stable): https://github.com/microsoft/WSL/releases. I did that a couple of hours ago and have been using Copilot through WSL again without an issue. |
vs-code-engineering
bot
removed
the
triage-needed
@bhavyaus sure thing! here you go: GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced.debug.useElectronFetcher": true,
"github.copilot.advanced.debug.useNodeFetcher": false,
"github.copilot.advanced.debug.useNodeFetchFetcher": trueConnecting to https://api.github.com:
Connecting to https://api.business.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. @jascomp thanks for the tip, but I'm on a remote linux environment, not Windows. Worth noting that when I reload VSCode, the first message or two will succeed, but then all subsequent messages hang. |
|
Please append the Copilot Chat and the Remote Extension Host log from when this happens. ( Have you tried updating WSL as suggested in the discussion you linked to? |
|
@chrmarti 👍 here's the output: GitHub Copilot Chat: Extension Host (Remote): I'm working on a mac, connected to a remote linux (ubuntu) host via ssh, so don't think WSL applies to me, right? iiuc, that's for Windows. |
|
@chrmarti correct. WSL should not apply, but I do think it is a possible clue. Are you able to confirm the remote Linux machine has been updated? |
|
Missed that you're not on Windows. Could you try adding the following to your user settings ( "github.copilot.advanced.debug.useNodeFetcher": trueThen reload VS Code and retry. |
|
update: I rebooted the remote linux host, and so far, copilot + chat are working again 🎉 If I start having trouble again, I will try |
|
I'm experiencing the same issue. Copilot starts working for couple of prompts after reloading VSC's window, but then it stops responding. I have no network issues or whatsoever. It appears to be related to VS Code's extension host. Whenever Copilot malfunctions, I also encounter problems launching the Python debugger. I've tried clearing VS Code's cache, uninstalling and reinstalling all extensions, and even reinstalling VS Code itself. Unfortunately, nothing has resolved the problem. Source control also stops working correctly when Copilot malfunctions. It seems like a VSC issue. System InformationApple M3 Max (16 x 2400) Extensionscopilot v1.253.0 Here's Copilot's diagnostic report: GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced.debug.useElectronFetcher": true,
"github.copilot.advanced.debug.useNodeFetcher": true,
"github.copilot.advanced.debug.useNodeFetchFetcher": trueConnecting to https://api.github.com:
Connecting to https://api.individual.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
|
I'm sad to report it's happening again to me. @chrmarti , fyi applied that setting ☝ as you suggested, but it did not fix the issue. |
|
@ahmadomira Since you mention SCM: There is an issue in the Python extension that seems to affect SCM. Could you try without the Python extension or update to its latest pre-release version that has a fix to check if that affects this issue? (microsoft/vscode-python#24611) |
|
Hi @chrmarti, Updating the Python extension to the latest pre-release version (microsoft/vscode-python#24611) appears to have fixed all issues immediately. Copilot, SCM, and the Python debugger are all working correctly. I've been using it for a couple of hours without encountering any problems. Thank you! |
|
@etmoore Could you try the same? The timeouts you are seeing in the diagnostics suggest this might be the same problem. |
|
@chrmarti :( switched to Python plugin pre-release version, but unfortunately did not fix the issue. Still seeing the same error: 
|
|
@chrmarti Same problem here. I tried the pre-release Python extension, but the problem was not solved. I also tried disabling all extensions except Copilot, but the problem was not solved. I think this problem may be related to the proxy. Copilot did not use the proxy correctly.，I used SSH connect to a remote machine, it is network-isolated and can only access the network through a proxy, and I set env I tested my connection according to https://docs.github.com/en/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#diagnosing-network-issues.
curl --verbose https://copilot-proxy.githubusercontent.com/_ping* Uses proxy env variable https_proxy == 'http://192.168.1.108:7892'
* Trying 192.168.1.108:7892...
* Connected to 192.168.1.108 (192.168.1.108) port 7892 (#0)
* allocate connect buffer
* Establish HTTP proxy tunnel to copilot-proxy.githubusercontent.com:443
> CONNECT copilot-proxy.githubusercontent.com:443 HTTP/1.1
> Host: copilot-proxy.githubusercontent.com:443
> User-Agent: curl/7.87.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* CONNECT phase completed
* CONNECT tunnel established, response 200
* ALPN: offers h2
* ALPN: offers http/1.1
* CAfile: /opt/anaconda3/ssl/cacert.pem
* CApath: /usr/lib/ssl/certs
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Client hello (1):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Server hello (2):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Certificate (11):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, CERT verify (15):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=*.githubusercontent.com
* start date: Jun 20 00:00:00 2024 GMT
* expire date: Jun 19 23:59:59 2025 GMT
* subjectAltName: host "copilot-proxy.githubusercontent.com" matched cert's "*.githubusercontent.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* h2h3 [:method: GET]
* h2h3 [:path: /_ping]
* h2h3 [:scheme: https]
* h2h3 [:authority: copilot-proxy.githubusercontent.com]
* h2h3 [user-agent: curl/7.87.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x9e23b0)
> GET /_ping HTTP/2
> Host: copilot-proxy.githubusercontent.com
> user-agent: curl/7.87.0
> accept: */*
>
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< content-security-policy: default-src 'none'; sandbox
< content-type: application/json
< strict-transport-security: max-age=31536000
< content-length: 48
< date: Thu, 26 Dec 2024 08:44:45 GMT
< x-github-backend: Kubernetes
< x-github-request-id: 35D3:1379B9:5E540C:605FCC:676D177D
<
{"now":1735202685,"status":"ok","ns1":"200 OK"}
* Connection #0 to host 192.168.1.108 left intactBut when I try
|
|
@jalenzz Are you still seeing this with the latest Python extension version 2024.22.1? (Yours also looks like microsoft/vscode-python#24611 which is now fixed in the latest stable Python extension release.) |
|
@chrmarti The problem seems to be gone with the latest Python extension version 2024.22.1. Thanks ! |
|
I'm no longer seeing the issue 🎉 |
|
Great, thanks for the update. Closing the issue. |
Type: Bug
Chat keeps failing. See "Sorry, your request failed. Please try again. Request id: e06234e0-3530-440a-8f5b-550713d60e33". Logs show errors like:
Extension version: 0.23.1
VS Code version: Code 1.96.0 (Universal) (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux x64 6.2.0-1016-aws
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Connection to 'SSH: dev' could not be established Canceled
Connection to 'SSH: dev' could not be established Canceled
Connection to 'SSH: dev' could not be established Canceled
A/B Experiments
The text was updated successfully, but these errors were encountered: