-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Crash after installing continue #3168
Comments
Hi @hisalock , thanks for the heads up here. Any chance you're able to view the Continue logs before it crashes? https://docs.continue.dev/troubleshooting#check-the-logs |
sorry, i'm not used to using the console, i hope this is what you want... Fetch finished loading: GET "". |
I'm another user seeing the same behaviour on Debian bookworm (12.2). The behaviour is the same regardless of whether I use the release or pre-release version of Continue. This is a fresh install of VSCode version 1.95.3 with only a few extensions installed (docker, F#...). These are the logs from when I enable Continue. Let me know if there's anything else I can do to help narrow down the cause.
|
Thanks for the +1s here all, unfortunately it looks like our logs are a bit sparse and not really providing any useful info as to what the root of the problem is. The only relevant line appears to be this:
Which doesn't provide much context. If any folks are willing/interested in helping debug this, I think attempting to build the extension locally off of Also curious if folks are able to install the JetBrains extension without it crashing on Debian Bookworm. |
I am able to install the extension with JetBrains Rider RD-243.21565.191, although it doesn't actually allow me to select a model when I try to use it. |
Could you point me in the direction of the build instructions, please? |
This likely implies that the GUI is unable to connect to JB.
https://github.com/continuedev/continue/blob/main/extensions/intellij/CONTRIBUTING.md Let me know if you have any issues/questions! This would be super helpful if you're able to figure out what's causing the GUI to connect with our JB logic. |
Thank you, Patrick, although I'm concentrating on VSCode. For anyone who stumbles across this issue, the VSCode extension instructions can be found at https://github.com/continuedev/continue/blob/main/extensions/vscode/CONTRIBUTING.md I have managed to narrow down the cause of the issue to the LanceDB dependency. I believe this is due to the fact that my CPU does not support AVX2. @hisalock Can you confirm whether yours supports AVX2? The AVX2 issue is described in #940, #2175, and lancedb/lance#2195. Following the hints there, I've installed version 0.8.23 of Continue and this does not crash the Extension Host. However, I'm also unable to use the free trial with this old version. Using an old version of Continue is not really a long-term solution. There is a possible workaround that involves building LanceDB from source, but I haven't tried that yet. |
I can confirm this works for both the latest release and pre-release versions of Continue. I had to downgrade a number of aws dependencies to get it to build, but Continue is working fine now. Again, it's difficult to know how long this will work with Continue updates. |
Interesting, thanks for the deep dive here @mjkaye ! I wasn't aware of the AVX2 issues. In the meantime, does the workaround Nate outlined here work for you, e.g. disabling indexing? Unfortunately I think that's the near-term solution. |
The workaround instructions are a little vague, so I'm not completely sure I've done it right. Adding the property If I have missed something in the instructions, please let me know and I'll test again. |
We are going to look into solving this by just disabling indexing by default for OS' that aren't supported by LanceDB. |
I'll be happy to test that when you do. |
Before submitting your bug report
Relevant environment info
Description
I tried to install on vscode the continue extension in vain. Vscode detects an extension that crashes. The bisect extension launches to identify which extension crashes. The continue extension is identified as the one that crashes.
To reproduce
Juste install "continue"
Log output
The text was updated successfully, but these errors were encountered: