-
Notifications
You must be signed in to change notification settings - Fork 11
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
LanguageServer fails to start #20
Comments
I get a very similar error. Already tried reinstalling and installing LanguageServer and SymbolServer manually but did not help
|
Looks like there are some compatibility issues with Julia 1.6 with the versions of LanguageServer.jl or one of its dependencies. We should bump the versions, and this will probably go away. Feel free to create a PR doing so; I haven't personally been using this package lately, so I'm not sure when I'll get to it. |
Indeed it looks like a compatibility issue between Julia 1.6 and the Manifest.toml file which is shipped with In the short term, a quick workaround should be to re-resolve the Manifest with Julia 1.6. @mguzmann and @danielw2904, since both of you you seem to have installed
Please try this workaround and report back if it didn't work. |
In the long run, I'm not sure how best to handle this. As we just saw with 1.6, I see several possibilities:
In order to avoid issues with options (2) and (3), we'd need There might be other options I did not think about. I think I would tend to favor option (3), which I find comfortable both from the viewpoint of an What do others think about this? |
I think the Manifest is supposed to be usable across Julia versions... There ought to be a bug open somewhere if this is the real root issue. What does the diff look like after resolving the Manifest? Are you sure resolve isn't just grabbing a new minor version release of a dep that's compatible with julia 1.6? To work around this if it is a bug, my preference would be number 2 of the options listed but number 3 would be fine as well. |
Well, actually I think there has never been any guarantee that the Manifest would be compatible across Julia versions; it just happens that incompatibilities never occurred in practice until recently with Julia 1.6. But issues like this one seem to be happening at various places in the Julia ecosystem, and it is now relatively clear that v1.5 & v1.6 manifests are not entirely compatible (I think this has something to do with the set of standard libraries differing between the two versions). See for example a recent discussion about this in the context of JuMP: https://discourse.julialang.org/t/jump-installation-issue-in-julia-v1-6/58721/8 In any case, I can confirm that:
so we actually need to do something about it: any manifest that we ship will be broken for some users. I would be fine with option (2); let's try that! I'll prepare a PR tomorrow and we'll see how things go. Do you think you'll be able to take some time reviewing it? (But no pressure! I think I can test this on my own to make sure the update goes smoothly before we ship it) |
I can certainly spend 10 minutes reviewing a simple version-bump/manifest-resolve PR tomorrow. If I don't review tomorrow for whatever reason, feel free to merge. |
The new Manifest.toml is tailored for Julia 1.6.0. Eglot-jl should still work with older Julia versions, since the environment is re-resolved at each server start to make sure it is compatible with the current Julia version. Fixes: non-Jedi#20
I am trying to use the LanguageServer with Emacs and julia 1.6. I am getting the following error when I call eglot.
The text was updated successfully, but these errors were encountered: