-
Notifications
You must be signed in to change notification settings - Fork 194
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
Failed to precompile LanguageServer #1024
Comments
I looked into this, and I'm pretty positive that this is simply the known problem that if two Julia instances try to precompile the same stuff, one (or both) crash. So it is enough to have two instances of VS Code that start the LS at the same time for the first time to trigger this. I don't think there is anything we can do, other than hope that someone finishes JuliaLang/julia#30174. |
@davidanthoff Sorry for the ping. I did not look up the PRs. |
I think this is fixed in Julia 1.6 |
Hi, I'm still getting a similar error in Julia 1.6:
I was previously using Julia 1.5 on macOS and everything was working properly, but whenever I tried to switch to Julia 1.6 (by updating the Julia executable path) I get this error if I open the Julia REPL inside VS Code. Switching the path back to Julia 1.5 makes this error go away. I was not running multiple VS Code instances though. This has been blocking me from switching to Julia 1.6 since the RC versions. Do you have any idea what's causing this? Thanks! |
Ok never mind, I have fixed the issue. It turns out the precompilation of VSCode somehow depends on how types are printed, and I was using SimpleTypePrint in my startup.jl, which overrides how types are shown (eg., |
Eh, I am using Julia 1.7 and it sill persists:
|
You're using a very old version of the extension. Please update. |
I literally just installed it from the marketplace in vscode |
It's very likely you're on an old version of VS Code itself. |
From crash reporting.
Message:
Stack trace:
We get a lot of crash reports like that... The existing error message is kind of too sparse to tell what is going on, but it is tricky to figure out how we could get more info... The only idea I have is to capture the whole stderr of the LS process into a buffer and send that with the crash reporting. But that would mean that nothing is shown in the output log for the LS in VS Code anymore, which seems really not ideal.
I also have no idea what might make precompile fail... Some ideas: maybe multiple instances of VS Code that all try to precompile at the same time and get into each other's way? Or maybe the VS Code extension is installed in a read-only location? The former seems kind of more likely to me...
The text was updated successfully, but these errors were encountered: