Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GitHub Copilot Chat Not Working After Extension Update #3366

Closed
CarlosSenobio opened this issue Dec 18, 2024 · 17 comments
Closed

GitHub Copilot Chat Not Working After Extension Update #3366

CarlosSenobio opened this issue Dec 18, 2024 · 17 comments
Assignees
@sbatten
Labels
bug Issue identified by VS Code Team member as probable bug free Copilot Free SKU Related

Comments

@CarlosSenobio
Copy link

Hello everyone, I would like to report an issue related to GitHub Copilot Chat. After updating the extension, it was necessary to reload Visual Studio Code. However, after doing so, GitHub Copilot stopped working. Clicking to accept the terms and start using it has no effect. I tried switching versions, but the issue persists. I will attach a video showing the problem. Thank you.

Issue:

  • Copilot Chat Extension Version: 0.23.2

  • VS Code Version:

    • Version: 1.96.1
    • Commit: 42b266171e51a016313f47d0c48aca9295b9cbb2
    • Date: 2024-12-17T17:50:05.206Z
    • Electron: 32.2.6
    • ElectronBuildId: 10629634
    • Chromium: 128.0.6613.186
    • Node.js: 20.18.1
    • V8: 12.8.374.38-electron.0
    • OS: Windows_NT x64 10.0.26100 (WSL Ubuntu)

  • Attachment: Video

Steps to Reproduce:
@github-actions github-actions bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Dec 18, 2024
@sbatten
Copy link
Member

sbatten commented Dec 18, 2024

@CarlosSenobio Can you enable trace logging via F1 > Set Log Level... and reload. When you reload, can you share logs in the Window Output channel. F1 > Show Output Channels...

@bhavyaus bhavyaus added the info-needed Issue requires more information from poster label Dec 18, 2024
@CarlosSenobio
Copy link
Author

@sbatten Here are the filtered logs for GitHub Copilot during the issue:

2024-12-18 18:23:02.005 [info] Can't use the Electron fetcher in this environment.
2024-12-18 18:23:02.005 [info] Using the Node fetch fetcher.
2024-12-18 18:23:02.005 [info] Initializing Git extension service.
2024-12-18 18:23:02.005 [info] Successfully activated the vscode.git extension.
2024-12-18 18:23:02.005 [info] Enablement state of the vscode.git extension: true.
2024-12-18 18:23:02.005 [info] Successfully registered Git commit message provider.
2024-12-18 18:23:03.311 [debug] [context keys] Updating context keys.
2024-12-18 18:23:03.861 [info] Logged in as CarlosSenobio
2024-12-18 18:23:04.734 [info] Got Copilot token for CarlosSenobio
2024-12-18 18:23:04.754 [debug] [LanguageModelAccess] UPDATING language models
2024-12-18 18:23:04.754 [trace] Resolving embedding model
2024-12-18 18:23:05.111 [info] copilot token chat_enabled: true, sku: monthly_subscriber
2024-12-18 18:23:05.117 [info] Registering default platform agent...
2024-12-18 18:23:05.117 [debug] onDidChangeSessionsHandler has token: true
2024-12-18 18:23:05.117 [debug] [context keys] Updating context keys.
2024-12-18 18:23:05.242 [info] Successfully activated the GitHub.vscode-pull-request-github extension.
2024-12-18 18:23:05.242 [info] [githubTitleAndDescriptionProvider] Initializing GitHub PR title and description provider provider.
2024-12-18 18:23:05.242 [info] Successfully registered GitHub PR title and description provider.
2024-12-18 18:23:05.554 [trace] Resolving embedding model
2024-12-18 18:23:05.655 [info] Fetched model metadata in 901ms 52a8d405-b788-43bd-a0e9-cc138b847490
2024-12-18 18:23:05.659 [trace] Resolved embedding model
2024-12-18 18:23:05.659 [trace] Resolved embedding model
2024-12-18 18:23:05.659 [info] activationBlocker from 'languageModelAccess' took for 2354ms
2024-12-18 18:23:05.660 [trace] Resolving chat model
2024-12-18 18:23:05.660 [trace] Resolved chat model
2024-12-18 18:23:05.797 [debug] [LanguageModelAccess] ADDED language model gpt-3.5-turbo
2024-12-18 18:23:05.797 [debug] [LanguageModelAccess] ADDED language model gpt-4
2024-12-18 18:23:06.062 [debug] [LanguageModelAccess] ADDED language model gpt-4o
2024-12-18 18:23:06.063 [debug] [LanguageModelAccess] ADDED language model gpt-4o-mini
2024-12-18 18:23:06.063 [debug] [LanguageModelAccess] ADDED language model gpt-4-0125-preview
2024-12-18 18:23:06.063 [debug] [LanguageModelAccess] ADDED language model o1-preview
2024-12-18 18:23:06.064 [debug] [LanguageModelAccess] ADDED language model o1-mini
2024-12-18 18:23:06.064 [debug] [LanguageModelAccess] ADDED language model claude-3.5-sonnet
2024-12-18 18:23:06.064 [debug] [LanguageModelAccess] DID UPDATE language models
2024-12-18 18:23:06.141 [debug] [LanguageModelAccess] UPDATING language models
2024-12-18 18:23:06.141 [trace] Resolving chat model
2024-12-18 18:23:06.141 [trace] Resolved chat model
2024-12-18 18:23:06.141 [debug] [LanguageModelAccess] DID UPDATE language models
2024-12-18 18:23:07.172 [trace] Resolving embedding model
2024-12-18 18:23:07.172 [trace] Resolved embedding model
2024-12-18 18:23:07.648 [trace] Resolving embedding model
2024-12-18 18:23:07.648 [trace] Resolved embedding model
2024-12-18 18:23:39.312 [debug] [context keys] Window state change. Needs offline check: false, active: true, focused: false.
2024-12-18 18:23:51.357 [debug] [context keys] Window state change. Needs offline check: false, active: true, focused: true.
2024-12-18 18:24:19.625 [debug] [context keys] Window state change. Needs offline check: false, active: true, focused: false.
2024-12-18 18:24:49.833 [debug] [context keys] Window state change. Needs offline check: false, active: true, focused: true.

It shows successful initialization, token fetching, and language model updates, but the issue persists when attempting to accept terms and enable the chat feature. Let me know if you need additional information or further logs.

@james-berkheimer
Copy link

I'm having a similar issue but not exactly the same. When using VS Code on my local Windows 10 machine Chat works fine after the update. But on any of my Linux based remote connections (SSH or WSL) I can't get chat to work. I'm not sure if this is a remote issue or a Linux issue.

https://imgur.com/VE5Wkie

@sbatten
Copy link
Member

sbatten commented Dec 18, 2024

We have found an issue with remote setups that we are still looking into a solution. In the meantime, the workaround is:
(from the remote window)

  1. uninstall the extension from the remote
  2. uninstall the extension again to remove it locally
  3. reload the window
  4. From your reloaded remote window, click "Use copilot for free"

This should install the extension again in the remote and unblock you

@lramos15 lramos15 added bug Issue identified by VS Code Team member as probable bug free Copilot Free SKU Related and removed info-needed Issue requires more information from poster triage-needed Issues needing to be assigned to the prospective feature owner labels Dec 18, 2024
@lramos15 lramos15 assigned sbatten and unassigned lramos15 Dec 18, 2024
@james-berkheimer
Copy link

We have found an issue with remote setups that we are still looking into a solution. In the meantime, the workaround is: (from the remote window)

  1. uninstall the extension from the remote
  2. uninstall the extension again to remove it locally
  3. reload the window
  4. From your reloaded remote window, click "Use copilot for free"

This should install the extension again in the remote and unblock you

OK that worked. But if I close the session it seems to stop working. So is this a per session temp workaround?

@sbatten
Copy link
Member

sbatten commented Dec 18, 2024

@james-berkheimer do you mean if you switch to a different remote? or when you go back to a local session? or when you come back to the same remote?

@CarlosSenobio
Copy link
Author

@sbatten It seems to have worked. I had to uninstall and reinstall the WSL extension twice, as well as disconnect from my GitHub/GitHub Copilot account before it started functioning properly. Thank you for the support! If further issues arise or if you need additional information, I will follow up.

@james-berkheimer
Copy link

james-berkheimer commented Dec 18, 2024 •
edited
Loading

@james-berkheimer do you mean if you switch to a different remote? or when you go back to a local session? or when you come back to the same remote?

@sbatten So I follow your steps and it works in the session I had opened. But if I close VS Code I have to repeat those steps to get Chat working again.

Or if I open a new window and connect to the remote session again, I have to repeat the steps.

@CarlosSenobio
Copy link
Author

@sbatten I conducted some tests, and it seems the issue is only resolved per session/workspace. For instance, after following the steps to install and reinstall the extensions to make GitHub Copilot Chat work, it sometimes still doesn't function properly. Furthermore, if I close VSCode or open another project in a different repository, it stops working again, requiring me to repeat the process, as @james-berkheimer mentioned above.

This was referenced Dec 19, 2024
Closed
Closed
Closed
@uqiu
Copy link

uqiu commented Dec 19, 2024

remove from both local and remote.
then reinstall.
fix this.

@sbatten
Copy link
Member

sbatten commented Dec 19, 2024

Thanks everyone on this issue for engaging and providing information to help us get this fixed. We will be posting the latest information in the linked issues above. Just to cross-post the most important information here, there will be a fix going into the next insiders release followed by a recovery build for stable.

@bpasero
Copy link
Member

bpasero commented Dec 19, 2024

The fix already landed in insiders, if people want to give it a try: You can give our preview releases a try from: https://code.visualstudio.com/insiders/

@vgdh
Copy link

vgdh commented Dec 19, 2024

remove from both local and remote.
then reinstall.
after reload the vscode the same issue occure. It doesn't work.

@rafamarquesi
Copy link

Hello everyone, I would like to report an issue related to GitHub Copilot Chat. After updating the extension, it was necessary to reload Visual Studio Code. However, after doing so, GitHub Copilot stopped working. Clicking to accept the terms and start using it has no effect. I tried switching versions, but the issue persists. I will attach a video showing the problem. Thank you.

Issue:

  • Copilot Chat Extension Version: 0.23.2

  • VS Code Version:

    • Version: 1.96.1
    • Commit: 42b266171e51a016313f47d0c48aca9295b9cbb2
    • Date: 2024-12-17T17:50:05.206Z
    • Electron: 32.2.6
    • ElectronBuildId: 10629634
    • Chromium: 128.0.6613.186
    • Node.js: 20.18.1
    • V8: 12.8.374.38-electron.0
    • OS: Windows_NT x64 10.0.26100 (WSL Ubuntu)

  • Attachment: Video

Steps to Reproduce:

I have the same problem.
Version: 1.96.1
Commit: 42b266171e51a016313f47d0c48aca9295b9cbb2
Date: 2024-12-17T17:50:05.206Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.8.0-51-generic snap

@joyceerhl
Copy link

This should be fixed with the latest 1.96.2 release which just went out.

@slogive
Copy link

slogive commented Dec 19, 2024

Nice

@slogive
Copy link

slogive commented Dec 19, 2024

Solved for me after update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbatten sbatten

Labels
bug Issue identified by VS Code Team member as probable bug free Copilot Free SKU Related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests