microsoft / vscode-copilot-release

Feedback on GitHub Copilot Chat UX in Visual Studio Code.
https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat
Creative Commons Attribution 4.0 International
328 stars 31 forks source link

GitHub Copilot Chat: v0.10.0 gives Error Code: SELF_SIGNED_CERT_IN_CHAIN #541

Closed ikolaxis closed 2 months ago

ikolaxis commented 11 months ago

Steps to Reproduce:

  1. When I update to GitHub Copilot Chat: v0.10.0, the Copilot Chat stops working and responds to all my prompts with the following message: "Please check your firewall rules and network connection then try again. Error Code: SELF_SIGNED_CERT_IN_CHAIN"
  2. When I roll back to the older version v0.7.1, the Copilot Chat works properly.
lramos15 commented 11 months ago

Does your corporate firewall properly allow https://api.githubcopilot.com

You can also try disabling the strict proxy SSL setting: http.proxyStrictSSL

ikolaxis commented 11 months ago

Does your corporate firewall properly allow https://api.githubcopilot.com

You can also try disabling the strict proxy SSL setting: http.proxyStrictSSL

From my browser, when I navigate to https://api.githubcopilot.com/ I get an HTML page with the message "404 page not found". The corporate firewall does not seem to forbid this page; otherwise, I would have gotten a different HTML page informing me that the corporate firewall prohibits access to the page.

I disabled the strict proxy SSL setting, but the same problem persists (this time with the latest version of GitHub Copilot Chat v0.10.1). I also tried disabling system certificates; once more, I got the same problem. This is the latest settings.json from my VS Code: { "redhat.telemetry.enabled": false, "git.autofetch": true, "editor.minimap.enabled": false, "workbench.colorTheme": "Visual Studio Dark", "http.proxyStrictSSL": false, "http.systemCertificates": false, "http.proxyAuthorization": null }

stefz0 commented 11 months ago

Experiencing the same issue.

puppetSpace commented 11 months ago

I'm getting this error too. Our company has SelfSignedcertificates. Didn't have this issue with previous versions

Copilot: v1.135.0 Copilot chat: v0.10.1 VsCode: 1.84.2

Addibro commented 11 months ago

Same issue for me, although not tried earlier versions.

Copilot: v1.135.0 Chat: v0.10.1

Version: 1.84.2 (Universal) Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e Date: 2023-11-09T10:52:33.687Z Electron: 25.9.2 ElectronBuildId: 24603566 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Darwin arm64 22.5.0

lramos15 commented 11 months ago

We have an attempted fix that will be out on Monday in the latest insiders + pre-release. Thanks for your patience 🙏

Sudhanva10 commented 11 months ago

@lramos15 Any Update on Patch Fix?

lramos15 commented 11 months ago

@lramos15 Any Update on Patch Fix?

We're doing some experimental patch work to try and fix this.

In the latest pre-release and insiders please try the following setting and then restart the application

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}
Addibro commented 11 months ago

@lramos15 Any Update on Patch Fix?

We're doing some experimental patch work to try and fix this.

In the latest pre-release and insiders please try the following setting and then restart the application

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

Added this and restarted but no luck yet

puppetSpace commented 11 months ago

@lramos15 Any Update on Patch Fix?

We're doing some experimental patch work to try and fix this.

In the latest pre-release and insiders please try the following setting and then restart the application

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

Installed insiders edition. Added that setting, but it didn't solved the issue

stefz0 commented 11 months ago

@lramos15 Any Update on Patch Fix?

We're doing some experimental patch work to try and fix this. In the latest pre-release and insiders please try the following setting and then restart the application

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

Added this and restarted but no luck yet

Did the same, no luck

lramos15 commented 11 months ago

Just to confirm you're on insiders with v0.11.2023111501 or greater of the extension

puppetSpace commented 11 months ago

I am on v0.11.2023111501. Just tried again and i get a different error: Please check your firewall rules and network connection then try again. Error Code: ECONNRESET.

chrmarti commented 11 months ago

Could you install the Network Proxy Test extension (https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test) and check the output of F1 > Network Proxy Test: Test Connection in VS Code?

When asked for the URL enter https://api.githubcopilot.com/. This should respond with a 404 Not Found status, that is expected, but maybe you get something else. Please share the output of this (make sure to remove any sensitive information first).

puppetSpace commented 11 months ago

https://api.githubcopilot.com/

VS Code 1.85.0-insider (54821ee1f14beca4866abd7de86175b4794b030d)
Network Proxy Test 0.0.8
win32 10.0.22621 x64

Settings:
- http.proxy: 
- http.proxyAuthorization: null
- http.proxyStrictSSL: true
- http.proxySupport: override
- http.systemCertificates: true

Environment variables:

Sending GET request to https://api.githubcopilot.com/...
Received error: read ECONNRESET (ECONNRESET)
Retrying while ignoring certificate issues to collect information on the certificate chain.

Sending GET request to https://api.githubcopilot.com/ (allowing unauthorized)...
Received error: read ECONNRESET (ECONNRESET)

I'm going to check with our network-team if the URl is not blacklisted

Sudhanva10 commented 11 months ago

@chrmarti Settings:

Environment variables:

Sending GET request to https://api.githubcopilot.com/... Received response:

puppetSpace commented 11 months ago

https://api.githubcopilot.com/

VS Code 1.85.0-insider (54821ee1f14beca4866abd7de86175b4794b030d)
Network Proxy Test 0.0.8
win32 10.0.22621 x64

Settings:
- http.proxy: 
- http.proxyAuthorization: null
- http.proxyStrictSSL: true
- http.proxySupport: override
- http.systemCertificates: true

Environment variables:

Sending GET request to https://api.githubcopilot.com/...
Received error: read ECONNRESET (ECONNRESET)
Retrying while ignoring certificate issues to collect information on the certificate chain.

Sending GET request to https://api.githubcopilot.com/ (allowing unauthorized)...
Received error: read ECONNRESET (ECONNRESET)

I'm going to check with our network-team if the URl is not blacklisted

Url is now whitelisted. now it works. I removed the setting you proposed and tried again. Then I get the certificate error again. So the setting works for the insider edition

chrmarti commented 11 months ago

Thanks @puppetSpace for confirming!

@Sudhanva10 That looks good and suggests GitHub Copilot Chat should work with the Node fetcher. Please make sure you are using the latest VS Code Insiders (http://code.visualstudio.com/insiders/) and VS Code Chat pre-release (currently v0.11.2023111601) versions and add the following user setting:

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}
ikolaxis commented 11 months ago

Hi @chrmarti, thanks a lot for providing a fix! I just tested it, and it works with the latest VS Code Insiders (v1.85.0-insider) and GitHub Copilot Chat (v0.11.2023111701). Please note it only works with the following settings.json; any change in the following params results in the reported error: { "http.proxyStrictSSL": false, "http.proxyAuthorization": null, "http.proxySupport": "override", "http.systemCertificates": true, "github.copilot.advanced": { "debug.useNodeFetcher": true } }

qwertycody commented 10 months ago

Hi @chrmarti, thanks a lot for providing a fix! I just tested it, and it works with the latest VS Code Insiders (v1.85.0-insider) and GitHub Copilot Chat (v0.11.2023111701). Please note it only works with the following settings.json; any change in the following params results in the reported error: { "http.proxyStrictSSL": false, "http.proxyAuthorization": null, "http.proxySupport": "override", "http.systemCertificates": true, "github.copilot.advanced": { "debug.useNodeFetcher": true } }

@ikolaxis - tried this fix and it did not work for me when I last attempted on a corporate network

carlosgutrod commented 10 months ago

Hi @chrmarti, thanks a lot for providing a fix! I just tested it, and it works with the latest VS Code Insiders (v1.85.0-insider) and GitHub Copilot Chat (v0.11.2023111701). Please note it only works with the following settings.json; any change in the following params results in the reported error: { "http.proxyStrictSSL": false, "http.proxyAuthorization": null, "http.proxySupport": "override", "http.systemCertificates": true, "github.copilot.advanced": { "debug.useNodeFetcher": true } }

This work for me. Corporate ZScaler in the middle.

Version: 1.85.0 (user setup) Commit: af28b32d7e553898b2a91af498b1fb666fdebe0c Date: 2023-12-06T20:48:09.019Z Electron: 25.9.7 ElectronBuildId: 25551756 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.19045

ashrafsarhan commented 10 months ago

I have fixed a similar issue by installing the following vscode extension on my macOs: Mac CA VSCode

yusufk commented 10 months ago

I have fixed a similar issue by installing the following vscode extension on my macOs: Mac CA VSCode

Thanks @ashrafsarhan - that worked for me too!

chrmarti commented 10 months ago

Mac CA VSCode additionally reads the CAs from '/System/Library/Keychains/SystemRootCertificates.keychain'. I will investigate if that would make sense to add by default.

Anas-Alhariri commented 10 months ago

@lramos15 Any Update on Patch Fix?

We're doing some experimental patch work to try and fix this.

In the latest pre-release and insiders please try the following setting and then restart the application

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

This worked for me.

I have Http: Proxy Strict SSL disabled in VS Code

sean-rowe commented 9 months ago

I've tried all of the solutions but nothing works. I have the newest version installed. Here are my logs


2024-01-30 12:47:39.720 [info] [gitExtensionService] Successfully activated the vscode.git extension.
2024-01-30 12:47:39.720 [info] [gitExtensionService] Enablement state of the vscode.git extension: true.
2024-01-30 12:47:39.720 [info] [gitExtensionService] Successfully registered Git commit message provider.
2024-01-30 12:47:40.760 [info] [auth] Logged in as xxxxxxx
2024-01-30 12:47:41.479 [info] [chat] copilot token chat_enabled: true
2024-01-30 12:47:41.479 [info] [githubTitleAndDescriptionProvider] Initializing GitHub PR title and description provider provider.
2024-01-30 12:47:41.479 [info] [githubTitleAndDescriptionProvider] GitHub.vscode-pull-request-github extension is not yet activated.
2024-01-30 12:47:41.479 [info] [auth] Got Copilot token for xxxxxxx
2024-01-30 12:47:41.644 [info] [auth] Logged in as xxxxxxx
2024-01-30 12:47:41.692 [info] [chat] copilot token chat_enabled: true
2024-01-30 12:47:41.692 [info] [auth] Got Copilot token for xxxxxxx
2024-01-30 12:47:48.458 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-30 12:47:48.459 [info] [chat fetch] modelMaxTokenWindow 4096
2024-01-30 12:47:48.459 [info] [chat fetch] chat model gpt-4
2024-01-30 12:47:48.684 [info] [extension] Error on conversation request: mU: certificate has expired
    at ude (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:119:29507)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at pBe (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:119:31529)
    at Zy.fetch (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:1242:10832)
    at cce (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:194:1926)
    at t.fetchMany (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:194:6659)
    at t.fetchOne (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:194:5864)
    at n1.fetchConversationResponse (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:1256:2000)
    at n1._provideResponseWithProgress (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:1256:1471)
    at n1.provideResponseWithProgress (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:1254:2086)
    at s.x (/Users/xxxxxxx/.vscode/extensions/github.copilot-chat-0.11.1/dist/extension.js:1266:1022)
    at f.$invokeAgent (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:141:128938)
chrmarti commented 9 months ago

@lramos15 Which URL does this error occur with? The hostname would be of main interest, maybe the mentioned api.githubcopilot.com? It seems the root certificate for that has expired.

chrmarti commented 9 months ago

@sean-rowe Are you behind a network proxy? Which version of VS Code are you using and on which OS?

sean-rowe commented 9 months ago

@lramos15 Which URL does this error occur with? The hostname would be of main interest, maybe the mentioned api.githubcopilot.com? It seems the root certificate for that has expired.

It's the api.githubpilot.com address. I'm behind a corporate firewall but I can hit the api url and get a 404, so I don't think the firewall is blocking the site.

I'm on a Mac with the latest version of vscode installed

chrmarti commented 9 months ago

@sean-rowe Could you install the Network Proxy Test extension (https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test) and check the output of F1 > Network Proxy Test: Test Connection in VS Code? Enter https://api.githubcopilot.com when asked for the URL.

That will use the same certificates as when using the node fetcher: https://github.com/microsoft/vscode-copilot-release/issues/541#issuecomment-1814187850

prock13 commented 9 months ago

installing Mac CA VSCode got it working for me. Thank you

diptesh-bose commented 8 months ago

@lramos15 Any Update on Patch Fix?

We're doing some experimental patch work to try and fix this.

In the latest pre-release and insiders please try the following setting and then restart the application

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

this worked

yuliankarapetkov commented 7 months ago

I'm using v0.13.0 and I started getting random errors today:

Please check your firewall rules and network connection then try again. Error Code: ERR_HTTP2_STREAM_ERROR.

Then:

unhandled status from server: 400 Bad Request

and:

Sorry, no response was returned.

And finally:

503

.container { margin: 50px auto 40px auto; width: 600px; text-align: center; } a { color: #4183c4; text-decoration: none; } a:hover { text-decoration: underline; } h1 { letter-spacing: -1px; line-height: 60px; font-size: 60px; font-weight: 100; margin: 0px; text-shadow: 0 1px 0 #fff; } p { color: rgba(0, 0, 0, 0.5); margin: 10px 0 10px; font-size: 18px; font-weight: 200; line-height: 1.6em;} ul { list-style: none; margin: 25px 0; padding: 0; } li { display: table-cell; font-weight: bold; width: 1%; } .logo { display: inline-block; margin-top: 35px; } .logo-img-2x { display: none; } @media only screen and (-webkit-min-device-pixel-ratio: 2), only screen and ( min--moz-device-pixel-ratio: 2), only screen and ( -o-min-device-pixel-ratio: 2/1), only screen and ( min-device-pixel-ratio: 2), only screen and ( min-resolution: 192dpi), only screen and ( min-resolution: 2dppx) { .logo-img-1x { display: none; } .logo-img-2x { display: inline-block; } } #suggestions { margin-top: 35px; color: #ccc; } #suggestions a { color: #666666; font-weight: 200; font-size: 14px; margin: 0 10px; }

<img width="200" src="data:image/png;base64...">

<p><strong>No server is currently available to service your request.</strong></p>
<p>Sorry about that. Please try refreshing and contact us if the problem persists.</p>
<div id="suggestions">
<a href="https://github.com/contact">Contact Support</a> &mdash;
<a href="https://www.githubstatus.com">GitHub Status</a> &mdash;
<a href="https://twitter.com/githubstatus">@githubstatus</a>
</div>

<a href="/" class="logo logo-img-1x">
<img width="32" height="32" title="" alt="" src="data:image/png;base64..." />
</a>

<a href="/" class="logo logo-img-2x">
<img width="32" height="32" title="" alt="" src="data:image/png;base64..." />
</a>
</div>
chrmarti commented 7 months ago

There seems to be an issue with the service. This is tracked as https://github.com/microsoft/vscode-copilot-release/issues/1021 on our side.

Let's keep this issue for the SELF_SIGNED_CERT_IN_CHAIN error.

BioTeq commented 6 months ago

Hi @chrmarti, thanks a lot for providing a fix! I just tested it, and it works with the latest VS Code Insiders (v1.85.0-insider) and GitHub Copilot Chat (v0.11.2023111701). Please note it only works with the following settings.json; any change in the following params results in the reported error: { "http.proxyStrictSSL": false, "http.proxyAuthorization": null, "http.proxySupport": "override", "http.systemCertificates": true, "github.copilot.advanced": { "debug.useNodeFetcher": true } }

This is the only thing that worked. Thank you!

simiyidtoyid commented 6 months ago

i get the err Please check your firewall rules and network connection then try again. Error Code: UNABLE_TO_VERIFY_LEAF_SIGNATUR

kyss2323 commented 6 months ago

Hi @chrmarti, thanks a lot for providing a fix! I just tested it, and it works with the latest VS Code Insiders (v1.85.0-insider) and GitHub Copilot Chat (v0.11.2023111701). Please note it only works with the following settings.json; any change in the following params results in the reported error: { "http.proxyStrictSSL": false, "http.proxyAuthorization": null, "http.proxySupport": "override", "http.systemCertificates": true, "github.copilot.advanced": { "debug.useNodeFetcher": true } }

it work for me !!! Thanks you

SantiGarzonD commented 6 months ago

Hi this worked for me also. Thank you very much!

Thanks @puppetSpace for confirming!

@Sudhanva10 That looks good and suggests GitHub Copilot Chat should work with the Node fetcher. Please make sure you are using the latest VS Code Insiders (http://code.visualstudio.com/insiders/) and VS Code Chat pre-release (currently v0.11.2023111601) versions and add the following user setting:

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}
sumpiseth commented 6 months ago

Hi @chrmarti, thanks a lot for providing a fix! I just tested it, and it works with the latest VS Code Insiders (v1.85.0-insider) and GitHub Copilot Chat (v0.11.2023111701). Please note it only works with the following settings.json; any change in the following params results in the reported error: { "http.proxyStrictSSL": false, "http.proxyAuthorization": null, "http.proxySupport": "override", "http.systemCertificates": true, "github.copilot.advanced": { "debug.useNodeFetcher": true } }

it work for me !! Thank you.

erenken commented 5 months ago

I am on a corporate VPN and many levels of firewall and scanning. I do know that they do intercept ALL SSL traffic and inject their own certificate.

2024-05-03 15:50:27.013 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-05-03 15:50:27.013 [info] [chat fetch] modelMaxPromptTokens 3072
2024-05-03 15:50:27.013 [info] [chat fetch] modelMaxResponseTokens 4096
2024-05-03 15:50:27.013 [info] [chat fetch] chat model gpt-4
2024-05-03 15:50:27.107 [info] [extension] Error on conversation request: dee: self signed certificate in certificate chain
    at HPe (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:97:29553)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at act (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:97:31578)
    at _9.fetch (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:1141:23146)
    at s2e (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:1107:5216)
    at o0.fetchMany (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:1107:10697)
    at o0.fetchOne (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:1107:9639)
    at t6.fetchConversationResponse (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:866:2807)
    at t6._provideResponseWithProgress (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:866:1626)
    at t6.provideResponseWithProgress (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:864:4167)
    at i.y (c:\Users\eric.renken\.vscode\extensions\github.copilot-chat-0.15.0\dist\extension.js:876:1460)
    at n.$invokeAgent (c:\Users\eric.renken\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:44194)

I am running:

VS Code 1.89.0 GitHub Copilot 1.186.0 GitHub Copilot Chat 0.15.0

It doesn't appear to use Windows Certificate store as a validation level, it would be nice if it did, and at the least would be really nice to have a settings check box to useNodeFetcher.

I know with Git SCM command line that if we don't have http.sslBackend schannel then they have to have http.sslverify=false. Once we switch to schannel we fixed the problem, so I don't know if this is somehow related. I know there are workaround and adding

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

Fixed mine as well, but it would be nice if we didn't have to, and I hope I provided some extra information.

chrmarti commented 5 months ago

We are currently testing with "debug.useElectronFetcher": true (an alternative to "debug.useNodeFetcher": true) by default in the latest pre-release versions of GitHub Copilot Chat (which requires VS Code Insiders). Please give that a try and let us know if there are any remaining issues.

RushilJalal commented 4 months ago

I'm getting the same issue as well

chrmarti commented 4 months ago

@RushilJalal Could you use the latest VS Code Insiders (http://code.visualstudio.com/insiders/) and the latest GitHub Copilot Chat pre-release version and run F1 > Developer: GitHub Copilot Chat Diagnostics and share the output here?

RushilJalal commented 4 months ago

@chrmarti The problem occurred a few times in the afternoon but it works fine now. I shall follow your steps if the problem occurs again.

arnabbiswas1 commented 2 months ago

@chrmarti I am running latest VSCode 1.92.0 connected to WSL. I am getting the following error sporadically (Yesterday it worked most of the time and today it worked once or twice):

Please check your firewall rules and network connection then try again. Error Code: ETIMEDOUT

Here is the log (Github Copilot: Open Logs):

2024-08-08 14:21:52.490 [info] [streamChoices] request done: headerRequestId: [5b4d17fa-b6d2-4e53-b564-98108264bfcf] model deployment ID: [d086-20240807144915]
2024-08-08 14:22:28.198 [error] [default] Error sending telemetry FetchError: 
    at fetch (/home/arnabb/.vscode-server/extensions/github.copilot-1.221.0/node_modules/@adobe/helix-fetch/src/fetch/index.js:99:11)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at cachingFetch (/home/arnabb/.vscode-server/extensions/github.copilot-1.221.0/node_modules/@adobe/helix-fetch/src/fetch/index.js:288:16)
    at OO.fetch (/home/arnabb/.vscode-server/extensions/github.copilot-1.221.0/lib/src/network/helix.ts:96:22) {
  type: 'system',
  _name: 'FetchError',
  code: 'ETIMEDOUT',
  errno: undefined,
  erroredSysCall: undefined
}

Output of "Developer: GitHub Copilot Chat Diagnostics" when things are NOT working:

GitHub Copilot Chat

Network

User Settings:

  "github.copilot.advanced": {
    "debug.useElectronFetcher": true,
    "debug.useNodeFetcher": false
  }

Connecting to https://api.github.com:

Connecting to https://api.githubcopilot.com/_ping:

Documentation

In corporate networks: Troubleshooting firewall settings for GitHub Copilot.

Output of "Developer: GitHub Copilot Chat Diagnostics" when things are working:

## GitHub Copilot Chat

- Extension Version: 0.18.1 (prod)
- VS Code: vscode/1.92.0
- OS: Linux
- Remote Name: wsl

## Network

User Settings:
```json
  "github.copilot.advanced": {
    "debug.useElectronFetcher": true,
    "debug.useNodeFetcher": false
  }

Connecting to https://api.github.com:

Connecting to https://api.githubcopilot.com/_ping:

Documentation

In corporate networks: Troubleshooting firewall settings for GitHub Copilot.

sumonst21 commented 2 months ago

I noticed some unusual logs recently, not sure if its related to the outage that just happened:

# Github Copilot Output
2024-08-15 04:19:29.985 [info] [certificates] Removed 86 expired certificates
2024-08-15 04:19:30.728 [info] [fetcher] Using Helix fetcher.
2024-08-15 04:19:30.728 [info] [code-referencing] Public code references are enabled.
2024-08-15 04:19:30.729 [info] [auth] Sucessfully authenticated
2024-08-15 04:44:31.223 [info] [fetcher] Using Helix fetcher.
2024-08-15 04:44:31.223 [info] [code-referencing] Public code references are enabled.
2024-08-15 05:27:54.668 [error] [ghostText] provideInlineCompletionItems: JsonParseError: Response content-type is text/html; charset=utf-8 (status=503)
    at ON.json (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\networking.ts:145:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at authFromGitHubToken (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\auth\copilotToken.ts:132:54)
    at auth (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:40:25)
    at authShowWarnings (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:131:25)
    at mM.getCopilotToken (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:174:33)
    at getUserKind (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\prompt\repository.ts:51:19)
    at np.updateExPValuesAndAssignments (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\experiments\features.ts:244:26)
    at getGhostText (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\ghostText\ghostText.ts:515:43)
    at calculateInlineCompletions (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\ghostText\ghostText.ts:77:20)
    at provideInlineCompletions (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\ghostText\ghostText.ts:140:20)
    at hU.provideInlineCompletionItems (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\ghostText\ghostText.ts:153:27)
    at Y.provideInlineCompletions (d:\Users\xxxxx21\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:120716) {
  code: 'ContentType=text/html; charset=utf-8'
}
## Repeated same until the last one below: 
2024-08-15 05:32:19.162 [error] [ghostText] provideInlineCompletionItems: JsonParseError: Response content-type is text/html; charset=utf-8 (status=503)
    at ON.json (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\networking.ts:145:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at authFromGitHubToken (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\auth\copilotToken.ts:132:54)
    at auth (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:40:25)
    at authShowWarnings (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:131:25)
    at mM.getCopilotToken (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:174:33)
    at getUserKind (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\prompt\repository.ts:51:19)
    at np.updateExPValuesAndAssignments (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\experiments\features.ts:244:26)
    at getGhostText (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\ghostText\ghostText.ts:515:43)
    at calculateInlineCompletions (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\ghostText\ghostText.ts:77:20)
    at provideInlineCompletions (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\ghostText\ghostText.ts:140:20)
    at hU.provideInlineCompletionItems (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\ghostText\ghostText.ts:153:27)
    at Y.provideInlineCompletions (d:\Users\xxxxx21\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:120716) {
  code: 'ContentType=text/html; charset=utf-8'
}
2024-08-15 05:32:23.471 [info] [certificates] Removed 86 expired certificates
2024-08-15 05:32:26.493 [error] [auth] auth: JsonParseError: Response content-type is text/html; charset=utf-8 (status=503)
    at ON.json (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\networking.ts:145:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at authFromGitHubToken (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\lib\src\auth\copilotToken.ts:132:54)
    at auth (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:40:25)
    at authShowWarnings (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:131:25)
    at mM.getCopilotToken (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:174:33)
    at attemptAuthentication (c:\Users\xxxxx21\.vscode\extensions\github.copilot-1.222.0\extension\src\auth.ts:58:9) {
  code: 'ContentType=text/html; charset=utf-8'
}
2024-08-15 05:32:26.493 [error] [auth] Response content-type is text/html; charset=utf-8 (status=503)
2024-08-15 05:44:42.379 [info] [certificates] Removed 86 expired certificates
2024-08-15 05:44:43.347 [info] [fetcher] Using Helix fetcher.
2024-08-15 05:44:43.348 [info] [code-referencing] Public code references are enabled.
2024-08-15 05:44:43.348 [info] [auth] Sucessfully authenticated
2024-08-15 05:44:52.863 [info] [fetchCompletions] request.response: [https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex/completions] took 873 ms

What's the '[certificates] Removed 86 expired certificates' means? wondering if it has to do something on my system?

chrmarti commented 2 months ago

@sumonst21 Since this is for GitHub Copilot (not Chat) please check https://github.com/orgs/community/discussions/categories/copilot and start a new discussion there. Thanks. (About the expired certificates: Make sure your system clock is correctly set. This is expected though.)

@arnabbiswas1 Continuing in https://github.com/microsoft/vscode-copilot-release/issues/1484.

Closing this issue since the original problem went stale. Thanks.

hankniel commented 2 months ago

override

thanks bro, it worked