Fork me on GitHub
#lsp
<
2022-02-03
>
papachan12:02:26

After upgrading clojure-lsp i see this output from emacs. is it a known issue? do i have to do something else?

LSP :: Connected to [clojure-lsp:21324/starting].
LSP :: clojure-lsp has exited (exited abnormally with code 193)
LSP :: clojure-lsp<1> has exited (exited abnormally with code 193)
Server clojure-lsp:21324/starting exited with status exit(check corresponding stderr buffer for details). Do you want to restart it? (y or n) n

ericdallo13:02:49

Do you use Windows?

ericdallo13:02:11

I'm working on a fix for Windows users

papachan13:02:05

Yeah i am on windows

ericdallo13:02:25

I'm working on a Fix, you can use previous release meanwhile

ericdallo13:02:22

@U1ZJ06MMK could you try installing again?

ericdallo13:02:39

I changed the latest release windows binary to use previous graalvm version

papachan13:02:45

oh but i install it using scoop

ericdallo13:02:41

if you remove it and install again should work

ericdallo13:02:50

scoop will download latest release again which should be fixed

👍 1
papachan13:02:31

scoop install clojure-lsp
Installing 'clojure-lsp' (2022.02.01-20.02.32) [64bit]
Loading clojure-lsp-native-windows-amd64.zip from cache
Checking hash of clojure-lsp-native-windows-amd64.zip ... ok.
Extracting clojure-lsp-native-windows-amd64.zip ... done.
Linking ~\scoop\apps\clojure-lsp\current => ~\scoop\apps\clojure-lsp\2022.02.01-20.02.32
Creating shim for 'clojure-lsp'.
'clojure-lsp' (2022.02.01-20.02.32) was installed successfully!

papachan13:02:48

ok it have been reinstalled but it look like the same version

ericdallo13:02:55

it's the same version

ericdallo13:02:21

I made a override on the binary just to avoid passing through the release process

papachan13:02:07

yeah i understand

papachan13:02:30

same error on my side

papachan13:02:56

the clojure-lsp process complain and ask me to exit or restart

ericdallo13:02:07

hum, could you try running on terminal clojure-lsp --version

papachan13:02:13

maybe you can just send to me the binary and i override manually?

papachan13:02:13

but with the graalvm change?

ericdallo13:02:38

yes, it works on my windows machine

papachan13:02:54

yeah looks like it have done the fix

papachan13:02:10

i have my several clojure-lsp process running

papachan13:02:25

thank you again ! eric !

rafaeldelboni16:02:04

Hey hello, from version https://github.com/clojure-lsp/clojure-lsp/releases/tag/2022.01.22-01.31.09 onwards I can't have this in my deps.edn:

:clojure-lsp {:replace-deps {com.github.clojure-lsp/clojure-lsp {:mvn/version "2022.01.22-01.31.09"}}
                :main-opts ["-m" "clojure-lsp.main"]}
And run commands like clj -M:clojure-lsp format I'm missing something?

rafaeldelboni16:02:39

I'm getting this error:

Execution error (FileNotFoundException) at clojure.main/main (main.java:40).
Could not locate clojure_lsp/main__init.class, clojure_lsp/main.clj or clojure_lsp/main.cljc on classpath. Please check that namespaces with dashes use underscores in the Clojure file name.

ericdallo16:02:25

Yes! we made some changes on the jar, that jar contains only the necessary to be used as a JVM dependency, clojure-lsp.api in this case, for what you want you need to use the com.github.clojure-lsp/clojure-lsp-standalone since you are using functions from main/cli

ericdallo16:02:59

This is what lein-clojure-lsp is using as well

rafaeldelboni16:02:01

Nice! It worked!