ERR_HTTP2_STREAM_CANCEL

ashilent commented 10 months ago

VS Code Version: 1.85.1
OS Version: Windows_NT x64 10.0.19045
Logs: Please check your firewall rules and networking connection then try again. Error Code: ERR_HTTP2_STREAM_CANCEL

Steps to Reproduce:

Type into copilot chat in VS code. Every now and then this error comes up. Sometimes it works completely fine.

dpgithub87 commented 9 months ago

I am getting the same issue (inconsistent) but with MAC and VS code

haddad-yacine commented 9 months ago

me too

luismmp commented 9 months ago

Same error here

skavan commented 9 months ago

me too. using prerelease CoPilot chat (0.13.xxx) on win with vscode, it actually locks up Copilot Chat (stop sign just sits there), and requires a restart of vscode. Rolling back to the CoPilot chat release version (0.12) gives me intermittent ERR_HTTP2_STREAM_CANCEL.. but it eventually resolves.

chrmarti commented 9 months ago

Could you try adding:

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}

or:

"github.copilot.advanced": {
  "debug.useElectronFetcher": true
}

to your user settings. (F1 > Preferences: Open User Settings (JSON))

Both are experimental replacements for the current HTTP2 implementation Copilot Chat is using. The first might currently be more stable, the second is expected to stabilize a bit more and then become the default.

surprisequiona commented 8 months ago

I am finding that this is tied to the length of time between queries in CoPilot chat in vscode, but also whether or not I am performing SSL inspection on the traffic.

When the traffic is subject to SSL inspection, the inital conversation works fine but subsequent calls time out with the error referenced by @skavan

With traffic NOT subject to SSL inspection, the initial and subsequent conversations seem to work fine.

goliveic commented 8 months ago

Could you try adding:
"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}
or:
"github.copilot.advanced": {
  "debug.useElectronFetcher": true
}
to your user settings. (F1 > Preferences: Open User Settings (JSON))

Both are experimental replacements for the current HTTP2 implementation Copilot Chat is using. The first might currently be more stable, the second is expected to stabilize a bit more and then become the default.

Even adding this on Preferences, does not work for me.

agombert commented 8 months ago

same here

ptogladif commented 8 months ago

same here, with mac and vscode

swiching to pre-release solve it...

JustinTBrown commented 7 months ago

I am finding that this is tied to the length of time between queries in CoPilot chat in vscode, but also whether or not I am performing SSL inspection on the traffic.

I also seem to be getting this after a long delay between queries (eg. 12 hours)

Msekkdk commented 6 months ago

Has anyone found the cause of this issue? When our proxy is enabled we see this issue, disabling the proxy we dont see the issue.

adriannavw commented 6 months ago

also seem to be having the same issue. I have a VPN set up working on vscode with windows

JustACasual commented 6 months ago

I am also getting this after a short while. Restarting VS Code fixes it for some time. I am on Windows.

chelseaharalson commented 6 months ago

This is happening for me as well. It seems to timeout after 10 minutes and I have to restart VS Code.

JustACasual commented 6 months ago

Update: For me it turned out to be a certificate issue in my corporate network environment. VS Code is not trusting self signed root CAs. I solved it by activating extension "win-ca" and changing setting "Win-ca: Inject" to "Append".

The cert issue was visible in the copilot chat log, which can be accessed from the small copilot icon in the lower right corner in VS Code.

I found this workaround somewhere, didn't figure it out myself, but can't remember where...

fisforfaheem commented 4 months ago

This is happeing again sicking tired

chrmarti commented 4 months ago

Could you install the latest VS Code Insiders (https://code.visualstudio.com/insiders/) and the latest GitHub Copilot Chat pre-release (currently v0.17.2024062801), run F1 > Developer: GitHub Copilot Chat Diagnostics and share the output here?

fisforfaheem commented 4 months ago

Could you try adding:
"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}
or:
"github.copilot.advanced": {
  "debug.useElectronFetcher": true
}
to your user settings. (F1 > Preferences: Open User Settings (JSON))

Both are experimental replacements for the current HTTP2 implementation Copilot Chat is using. The first might currently be more stable, the second is expected to stabilize a bit more and then become the default.

any technical benfits?

fisforfaheem commented 4 months ago

Could you install the latest VS Code Insiders (https://code.visualstudio.com/insiders/) and the latest GitHub Copilot Chat pre-release (currently v0.17.2024062801), run F1 > Developer: GitHub Copilot Chat Diagnostics and share the output here?

Copilot

Version: 1.208.962
Build: nightly
Editor: vscode/1.90.2

Environment

http_proxy: n/a
https_proxy: n/a
no_proxy: n/a
SSL_CERT_FILE: n/a
SSL_CERT_DIR: n/a
OPENSSL_CONF: n/a

Feature Flags

Send Restricted Telemetry: enabled
Chat: enabled

Node setup

Number of root certificates: 141
Operating system: Darwin
Operating system version: 20.6.0
Operating system architecture: x64
NODE_OPTIONS: n/a
NODE_EXTRA_CA_CERTS: n/a
NODE_TLS_REJECT_UNAUTHORIZED: n/a
tls default min version: TLSv1.2
tls default max version: TLSv1.3

Network Configuration

Proxy host: n/a
Proxy port: n/a
Kerberos SPN: n/a
Reject unauthorized: disabled
Fetcher: HelixFetcher

Reachability

github.com: HTTP 200
api.github.com: HTTP 200
copilot-proxy.githubusercontent.com: HTTP 200
api.githubcopilot.com: HTTP 200
default.exp-tas.com: HTTP 200

VS Code Configuration

HTTP proxy:
HTTP proxy authentication: n/a
Proxy Strict SSL: true
Extension HTTP proxy support: override

Extensions

Is win-ca installed?: false
Is mac-ca installed?: false

Authentication

GitHub username: fisforfaheem

chrmarti commented 4 months ago

That looks good. Maybe try adding the following to the user settings JSON, it uses a different HTTP2 implementation (from Chromium) which might make a difference if the problem is indeed client-side:

"github.copilot.advanced": {
  "debug.useElectronFetcher": true
}

Julioevm commented 4 months ago

I had the same issue on macos after my company started using Global Protect, a vpn application. Solved it using this extension: https://marketplace.visualstudio.com/items?itemName=linhmtran168.mac-ca-vscode

chrmarti commented 3 months ago

There is a potential fix for this in the latest GitHub Copilot Chat pre-release (v0.18.2024071201). Please give that a try and let us know if this error still occurs. The pre-release version requires the latest VS Code Insiders (https://code.visualstudio.com/insiders/).

BrunoAPazetti commented 3 months ago

The reference from StackOverflow below worked for me:

https://stackoverflow.com/questions/71367058/self-signed-certificate-in-certificate-chain-on-github-copilot

"""1 - Install win-ca 2 - In the win-ca settings, switch Inject to append mode (it's not the default). 3 - Restart VsCode"""

chrmarti commented 3 months ago

It would be great to hear from someone who sees the ERR_HTTP2_STREAM_CANCEL if the fix in the latest GitHub Copilot Chat pre-release improves things. The pre-release version requires the latest VS Code Insiders (https://code.visualstudio.com/insiders/). Thanks.

sag1v commented 3 months ago

Thanks @chrmarti, when is it expected to be released as a stable version?

chrmarti commented 3 months ago

@sag1v In about 2 weeks alongside the next VS Code stable release (which doesn't have a fixed date).

sries-bhs commented 3 months ago

I also had the ERR_HTTP2_STREAM_CANCEL error. Using the Insiders version of VS-Code with the the latest prerelease verison of GitHub CoPilot did NOT work. I could fix it by setting BOTH values to true: "github.copilot.advanced": { "debug.useNodeFetcher": true, "debug.useElectronFetcher": true }

Now it does also work with the stable version of the GitHub CoPilot Chat

rzhao271 commented 3 months ago

I don't believe I've ever encountered this issue myself in the first place, but I'm considering this issue verification-found due to @sries-bhs's comment.

rzhao271 commented 3 months ago

Actually, @sag1v could you also try verifying this issue on the latest VS Code Insiders along with the latest GitHub Copilot Chat pre-release extension?

chrmarti commented 3 months ago

I don't have verification steps.

AashishKumar-3002 commented 3 months ago

Tried all the steps mentioned above including the insider version but the extension did not work. Facing the same issue

chrmarti commented 3 months ago

@AashishKumar-3002 Could you open a new issue with the GitHub Copilot Chat log (F1 > Output: Show Output Channels... > GitHub Copilot Chat) and the diagnostics output (F1 > Developer: GitHub Copliot Chat Diagnostics) using the latest VS Code Insiders and GitHub Copilot Chat versions?

vanBlayt commented 2 months ago

Has anyone found the cause of this issue? When our proxy is enabled we see this issue, disabling the proxy we dont see the issue.

same here

when i use charles to proxy network. it will happen on there

connor4312 commented 2 months ago

Reopening based on commenters' reports

microsoft / vscode-copilot-release