continuedev / continuedev/continue

Extension is not activating(Visual Studio Code)

Open
#3,009 53 comments 5 reactions 1 assignee View on GitHub

@Patrick-Erichsen is already working on this.

Since Nov 20, 2024.

area:dev-ex ide:vscode kind:bug no-stale os:windows
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
- OS: Windows 11
- Continue version:v0.8.57
- IDE version: VSCode 1.95.3
Description

I am getting an error like this ->"Error activating the Continue extension"
I have tried all the methods to check if my other extensions are conflicting with the activation of this extension, but i am still getting the same error. Below is the image of the error that is showing up.

image

To reproduce

-> Go to Visual Studio Code.
-> Open Extensions Section.
-> Install the extension "Continue-Codeastral, Claude, and more".
-> Try opening the extension.

Log output
2024-11-20 21:54:01.212 [info] Extension host with pid 7500 started
2024-11-20 21:54:01.330 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2024-11-20 21:54:01.343 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-11-20 21:54:01.437 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2024-11-20 21:54:01.655 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-11-20 21:54:01.895 [info] Eager extensions activated
2024-11-20 21:54:01.918 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:54:01.928 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:54:01.965 [info] ExtensionService#_doActivateExtension ecmel.vscode-html-css, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:54:32.013 [info] ExtensionService#_doActivateExtension Continue.continue, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:54:44.493 [error] Error: command 'continue.viewLogs' not found
    at mWe.n (vscode-file://vscode-app/c:/Users/dell/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1295:1341)
    at mWe.executeCommand (vscode-file://vscode-app/c:/Users/dell/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1295:1273)
2024-11-20 21:55:37.146 [info] Extension host terminating: renderer closed the MessagePort
2024-11-20 21:55:37.155 [info] Extension host with pid 7500 exiting with code 0
2024-11-20 21:55:37.799 [info] Extension host with pid 7524 started
2024-11-20 21:55:37.809 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-11-20 21:55:37.829 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: false, activationEvent: '*', root cause: vscode.git
2024-11-20 21:55:37.848 [info] ExtensionService#_doActivateExtension vscode.git, startup: false, activationEvent: '*'
2024-11-20 21:55:37.908 [info] ExtensionService#_doActivateExtension vscode.github, startup: false, activationEvent: '*'
2024-11-20 21:55:38.012 [info] Eager extensions activated
2024-11-20 21:55:38.020 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:55:38.024 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:55:40.391 [info] ExtensionService#_doActivateExtension Continue.continue, startup: false, activationEvent: 'onStartupFinished'
2024-11-20 21:56:26.023 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.