-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
Extension is not activating(Visual Studio Code) #3009
Comments
note, I had this error as well and fixed on this branch by adding the viewlogs command back to package.json |
Thank you for sharing the fix and pointing me to the branch! I tried adding the viewlogs command back to package.json as suggested and also done the other changes committed, but unfortunately, I'm still encountering the same error. Do you have any additional suggestions or insights on what else might be causing this? I’d greatly appreciate your help! |
Have you tried removing the project and recloning? A bit of a blunt approach but that would be a good way to guarantee you're starting from scratch; |
I had the same issue yesterday. In my case it was a simple solution. Due to work restrictions I always have to manually download the .vsix install file to update. Since I usually work on Windows I downloaded the windows version. However, this time I had to install on a Red Hat Enterprise Linux machine. At first I tried to install the Windows vsix on the linux machine which triggered the same error like yours. This morning I discovered my error and downloaded the linux version. Works flawless without the error now, so you might take a look at your vsix versions. |
I got the same error message. In my case the OS is Windows 11 running on ARM (Snapdragon X). Wonder if this could be a cause for the error... |
I've got same error. Neither installing from ms market nor installing from vsix amd64 version do work. |
Current error I am getting on Windows 11 running on ARM (Snapdragon X):
|
Same here (x86_64 under Windows with newest VS Code 1.96.3) |
@MarcoWel are there any logs you can also share? https://docs.continue.dev/troubleshooting#check-the-logs I think there are likely two separate issues for folks running into this more recently: |
@Patrick-Erichsen Here you go! Need to add that the extension worked flawlessly before, and now stopped working both on the local machine (Windows Server 2019 x86 AMD64) and the SSH extension host (Ubuntu 22 x86 AMD64) without any changes to the machines or their configuration.
|
Not likely. My CPU is Intel i7-12700 that supports FMA and AVX2. |
cc @RomneyDa here - there appears to be some URI issues here:
I believe we have fixes for these merged/in-progress but worth mentioning here. |
Just rechecked, the issue still persists for both the latest release and beta extension in VS Code. |
Got it working again - seems the Continue extension needs executable rights in the path This was blocked on our machines by GPO. For other extensions this is not necessary (it was probably not necessary for older revisions of the Continue extensions either, as we changed nothing on the configuration before it stopped working). |
Facing this issue on ubuntu/linux. Seems it appeared with a recent update? Re-enabling / reinstalling did not help |
@digiperfect-tech any additional logs you can share? @MarcoWel I don't believe we modified any permissions on the binary. That is odd that you had to manually do so. Haven't seen other reports of that so far at least. |
@Patrick-Erichsen that script at #839 fixes the issue on Windows 11 ARM64...definitely a long standing issue here |
@shanselman looks like LanceDB has support for windows arm64 now! lancedb/lancedb#1841 Planning to pull that in soon here. |
Still happening on NixOS:
|
Before submitting your bug report
Relevant environment info
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.
To reproduce
-> Go to Visual Studio Code.
-> Open Extensions Section.
-> Install the extension "Continue-Codeastral, Claude, and more".
-> Try opening the extension.
Log output
The text was updated successfully, but these errors were encountered: