vscode-copilot-release icon indicating copy to clipboard operation
vscode-copilot-release copied to clipboard

Problem GitHub Copilot Chat

Open sdheepakdba opened this issue 1 year ago • 25 comments

  • Copilot Chat Extension Version:12,109,155
  • VS Code Version:1.092
  • OS Version: Windows 10
  • Logs:

Errors :- Unable to resolve model with family selection: gpt-4

sdheepakdba avatar Jul 02 '24 20:07 sdheepakdba

@hediet Since today I have the same problem, I have windows 11 enterprice, it does not work neither in VS Code nor in Visual Studio 2022.

This is the last line of the problem in the visual studio code chat log: Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:49553) This is the last line of the problem in the visual studio 2022 chat log: [Conversations Information] [CopilotCompletions] Error while processing the event: The SSL connection could not be established, see inner exception.

leahrdt avatar Jul 02 '24 23:07 leahrdt

Hi, could you please share the logs from the Developer Tools (invoke command "Toggle Developer Tools" from the command palette (press F1 to open)) ?

ulugbekna avatar Jul 05 '24 11:07 ulugbekna

@ulugbekna 137 [Extension Host] [extension] Error: Unable to resolve chat model with family selection: gpt-4 at UA.getChatModel (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.2024062801\dist\extension.js:1317:2578) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ZT.getChatEndpoint (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.2024062801\dist\extension.js:1317:5768) at t.invoke (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.2024062801\dist\extension.js:839:3611) at aM._provideResponseWithProgress (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.2024062801\dist\extension.js:872:1222) at aM.provideResponseWithProgress (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.2024062801\dist\extension.js:870:4562) at n.y (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.2024062801\dist\extension.js:882:1826) at g.$invokeAgent (c:\Users\vmvv\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:50217)

leahrdt avatar Jul 05 '24 12:07 leahrdt

/duplicate https://github.com/microsoft/vscode-copilot-release/issues/1361

ulugbekna avatar Jul 05 '24 13:07 ulugbekna

Please update to VS Code 1.91.0 and GitHub Copilot Chat 0.17.0.

If it doesn't work with these versions, please run F1 > Developer: GitHub Copilot Chat Diagnostics and share the output here.

chrmarti avatar Jul 05 '24 14:07 chrmarti

@chrmarti I have VS Code 1.91.0 and GitHub Copilot Chat 0.17.0.

and I continued with the same problem:

workbench.desktop.main.js:sourcemap:139 [Extension Host] [extension] Error: Unable to resolve chat model with family selection: gpt-4 at UA.getChatModel (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:1317:2578) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ZT.getChatEndpoint (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:1317:5768) at t.invoke (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:839:3611) at aM._provideResponseWithProgress (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:872:1222) at aM.provideResponseWithProgress (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:870:4601) at n.y (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:882:1826) at g.$invokeAgent (c:\Users\vmvv\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:50217)

thank you

leahrdt avatar Jul 05 '24 14:07 leahrdt

Please run F1 > Developer: GitHub Copilot Chat Diagnostics and share the output here.

chrmarti avatar Jul 09 '24 08:07 chrmarti

Please run F1 > Developer: GitHub Copilot Chat Diagnostics and share the output here.

This is the output:

workbench.desktop.main.js:sourcemap:139 [Extension Host] [extension] Error: Unable to resolve chat model with family selection: gpt-4 at UA.getChatModel (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:1317:2578) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ZT.getChatEndpoint (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:1317:5768) at t.invoke (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:839:3611) at aM._provideResponseWithProgress (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:872:1222) at aM.provideResponseWithProgress (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:870:4601) at n.y (c:\Users\vmvv.vscode\extensions\github.copilot-chat-0.17.0\dist\extension.js:882:1826) at g.$invokeAgent (c:\Users\vmvv\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:50217)

leahrdt avatar Jul 09 '24 13:07 leahrdt

@hediet Since today I have the same problem, I have windows 11 enterprice, it does not work neither in VS Code nor in Visual Studio 2022.

This is the last line of the problem in the visual studio code chat log: Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:49553) This is the last line of the problem in the visual studio 2022 chat log: [Conversations Information] [CopilotCompletions] Error while processing the event: The SSL connection could not be established, see inner exception.

I'm having the exact same problem and it started about a week ago...

brodrigz avatar Jul 10 '24 13:07 brodrigz

From chat diagnostics


DNS Lookup api.githubcopilot.com: 140.82.112.22

Fetching https://api.githubcopilot.com/_ping:
- Electron Fetcher: Error: net::ERR_CERT_DATE_INVALID
- Node Fetcher: Error: certificate has expired
- Helix Fetcher (configured): Error: certificate has expired

brodrigz avatar Jul 10 '24 13:07 brodrigz

@sacalata Thanks, 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 for https://api.githubcopilot.com in VS Code?

chrmarti avatar Jul 11 '24 09:07 chrmarti

@chrmarti Note: Make sure to replace all sensitive information with dummy values before sharing this output.

VS Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286) Network Proxy Test 0.0.11 win32 10.0.22631 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... vscode-proxy-agent: DIRECT 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)... vscode-proxy-agent: DIRECT Received error: read ECONNRESET (ECONNRESET)

leahrdt avatar Jul 12 '24 16:07 leahrdt

@leahrdt Are you behind a firewall that might need to allow-list api.githubcopilot.com?

Could you also run F1 > GitHub Copilot: Collect Diagnostics? That will check a few more hosts that are also needed by the GitHub Copilot extensions.

chrmarti avatar Jul 15 '24 08:07 chrmarti

@chrmarti This is the result of GitHub Copilot: Collect Diagnostics

Copilot

  • Version: 1.213.0
  • Build: prod
  • Editor: vscode/1.91.1

Environment

  • http_proxy: n/a
  • https_proxy: n/a
  • no_proxy: n/a
  • SSL_CERT_FILE: n/a
  • SSL_CERT_DIR: c:\Users\vmvv.vscode\extensions\ukoloff.win-ca-3.5.1\node_modules\win-ca\pem
  • OPENSSL_CONF: n/a

Feature Flags

  • Send Restricted Telemetry: disabled
  • Chat: enabled

Node setup

  • Number of root certificates: 141
  • Operating system: Windows_NT
  • Operating system version: 10.0.22631
  • 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: read ECONNRESET
  • 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?: true
  • Is mac-ca installed?: false

Authentication

  • GitHub username: leahrdt

leahrdt avatar Jul 15 '24 12:07 leahrdt

I had a similar or maybe even the same issue and got copilot chat working again adding the following setting (and restarting VS code afterwards):

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

See additional info here

benimue avatar Jul 15 '24 13:07 benimue

@leahrdt api.githubcopilot.com seems to be the only host that is not reachable. Please check with your IT and let them allow-list https://*.githubcopilot.com in the company network. Also see: https://docs.github.com/en/copilot/troubleshooting-github-copilot/troubleshooting-firewall-settings-for-github-copilot

chrmarti avatar Jul 15 '24 14:07 chrmarti

Perfect, it's solved! thank you

leahrdt avatar Jul 16 '24 11:07 leahrdt

@chrmarti Hello, Mr. Marti. This is my result. And, it's clear that both github.com and api.githubcopilot.com are not reachable. But I don't know how to put them into the allow-list. Could you please tell me the method in details? Besides, I'm not sure whether Is "win-ca" installed?: false is relevant to the error massage? Should I install the extension win-ca? Thanks for your attention.

Copilot

  • Version: 1.219.0
  • Build: prod
  • Editor: vscode/1.91.1

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: Windows_NT
  • Operating system version: 10.0.22631
  • 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: read ECONNRESET
  • api.github.com: HTTP 200
  • copilot-proxy.githubusercontent.com: HTTP 200
  • api.githubcopilot.com: read ECONNRESET
  • 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: Willaaaaaaa

Willaaaaaaa avatar Jul 29 '24 13:07 Willaaaaaaa

@Willaaaaaaa Is this in a company network? If so, please share the following documentation with your IT department asking them to allow-list the required hosts: https://docs.github.com/en/copilot/troubleshooting-github-copilot/troubleshooting-firewall-settings-for-github-copilot

chrmarti avatar Jul 30 '24 12:07 chrmarti

@chrmarti No, sir. I'm at home. I don't quite understand the documentation. Is there any possible solution that I can do myself? Sorry to bother you, but I'm really a beginner in computer science learning and have no idea on how to deal with such problem. It's so kind of you for replying me.

Willaaaaaaa avatar Jul 30 '24 15:07 Willaaaaaaa

@Willaaaaaaa The mixed reachability results look similar to what you might see with a firewall that needs to allow-list more hosts:

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

Maybe you are using some VPN? Could you also run F1 > Developer: GitHub Copilot Chat Diagnostics and share the result here?

chrmarti avatar Jul 31 '24 07:07 chrmarti

@chrmarti Yes, sir. I use VPN sometimes because I'm in China. But regardless of whether I use VPN or not, it will display an error message. Here are the results. Thanks again for your reply.

  • This is the result when I use VPN:

GitHub Copilot Chat

  • Extension Version: 0.17.1 (prod)
  • VS Code: vscode/1.91.1
  • OS: Windows

Network

User Settings:

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

DNS Lookup api.githubcopilot.com: 140.82.113.22

Fetching https://api.githubcopilot.com/_ping:

  • Electron Fetcher: HTTP 200
  • Node Fetcher: HTTP 200
  • Helix Fetcher (configured): Error: read ECONNRESET

  • And the result when not using VPN and only using home network:

GitHub Copilot Chat

  • Extension Version: 0.17.1 (prod)
  • VS Code: vscode/1.91.1
  • OS: Windows

Network

User Settings:

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

DNS Lookup api.githubcopilot.com: 140.82.113.21

Fetching https://api.githubcopilot.com/_ping:

  • Electron Fetcher: Error: net::ERR_CONNECTION_RESET
  • Node Fetcher: HTTP 200
  • Helix Fetcher (configured): Error: read ECONNRESET

Willaaaaaaa avatar Jul 31 '24 07:07 Willaaaaaaa

Given these results you could try adding the follow to your user settings (F1 > Preferences: Open User Settings (JSON)):

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

And then restart VS Code.

chrmarti avatar Jul 31 '24 08:07 chrmarti

@chrmarti OMG!! It really works!!!! You really are the smartest programmer I have ever met so far! Thank you, sir! Love you!

Willaaaaaaa avatar Jul 31 '24 08:07 Willaaaaaaa

Hey @chrmarti, this issue might need further attention.

@sdheepakdba, you can help us out by closing this issue if the problem no longer exists, or adding more information.

Thanks , Please close the request

sdheepakdba avatar Nov 29 '24 15:11 sdheepakdba

Hey @chrmarti, this issue might need further attention.

@sdheepakdba, you can help us out by closing this issue if the problem no longer exists, or adding more information.