-
Notifications
You must be signed in to change notification settings - Fork 81
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 throwing MethodError #1003
Comments
What version of Julia are you using? I suspect it's 1.7.0-beta, which is not guaranteed to be compatible. Try the latest master ( |
I'm using 1.6.3. I followed the install instructions for vim, so running julia --project=/home/jack/.julia/environments/nvim-lspconfig --startup-file=no --history-file=no -e 'ls_install_path = joinpath(get(DEPOT_PATH, 1, joinpath(homedir(), ".julia")), "environments", "nvim-lspconfig"); pushfirst!(LOAD_PATH, ls_install_path); using LanguageServer; popfirst!(LOAD_PATH); depot_path = get(ENV, "JULIA_DEPOT_PATH", ""); project_path = let; dirname(something( Base.load_path_expand(( p = get(ENV, "JULIA_PROJECT", nothing); p === nothing ? nothing : isempty(p) ? nothing : p )), Base.current_project(), get(Base.load_path(), 1, nothing), Base.load_path_expand("@v#.#"), )) end; @info "Running language server" VERSION pwd() project_path depot_path; server = LanguageServer.LanguageServerInstance(stdin, stdout, project_path, depot_path); server.runlinter = true; run(server)' Yields a process that hangs on the following message on the master branch
Is this the intended behavior? |
I think it would be helpful to fully state your environment:
|
I was getting the same error as @jarbus using |
Actually LanguageServer.jl seems to work now, I think it only crashes on scripts without an associated Project.toml file. Thanks for the help! |
Julia's Language Server has worked for me in the past, but is now throwing this error after a re-install and I can't figure out what's going on. Using the latest version and currently testing without an editor so I can catch debug info.
The text was updated successfully, but these errors were encountered: