-
Notifications
You must be signed in to change notification settings - Fork 75
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
Language server crashing #1233
Comments
Is this on Julia 1.10+? Is your code using any fancy new syntactical constructs? |
I get this error using Julia v1.9 and latest |
Note: May/may not relate to issue #1226 I'm on Win 10 Enterprise (22H2) / VSCode 1.81.1 w/ Julia extension 1.51.2... no other extensions loaded. I've gone so far as to uninstall the extension & VSCode & Julia, then do a clean reinstall of everything. Using Julia 1.9.3. When I load the LS extension, LS tries to start but crashes. I'll copy/paste the first bit of the output here and attach a text file with everything starting at "Please submit a bug report..." The first bit is:
It goes on like that for quite a few lines. Again, the bug report output is attached. Thanks. |
By way of follow-up... Now with VSCode 1.82.2 & Julia extension 1.52.2, upon loading I get:
If I open a REPL in VSCode, I can execute code there, but VSCode itself is unable to execute code. Thanks. |
It's likely that you have a invalid Julia file somewhere in your workspace (or one with very deeply nested expression trees). I think the next release of the extension might give you some hint as to which file is the issue. https://discourse.julialang.org/t/language-server-broken/104071 is very similar. |
Thanks. I shall go hunting once more... [So, I decided to drop a Daisycutter... uninstalled Julia and then completely deleted my .julia folder. Then I nuked the Julia extension. After reinstalling Julia and the extension, the Language Server now loads without a hitch. I think we can put this one to bed... suggest adding this as a form of tribal wisdom. There is such a section in the docs, right? ;) ] |
The text was updated successfully, but these errors were encountered: