Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2024-05-29

Channels

#calva
<
2024-05-29
>
Alexander Kouznetsov19:05:44

I started getting this error when running LSP from Calva. Does it look familiar? 

[Error - 12:29:23 PM] Clojure Language Client client: couldn't create connection to server.
Error: spawn Unknown system error -86
    at ChildProcess.spawn (node:internal/child_process:414:11)
    at Object.spawn (node:child_process:799:9)
    at transports (/Users/a/.vscode/extensions/betterthantomorrow.calva-2.0.452/node_modules/vscode-languageclient/lib/node/main.js:426:46)
    at x.connection [as createConnection] (/Users/a/.vscode/extensions/betterthantomorrow.calva-2.0.452/node_modules/vscode-languageclient/lib/common/client.js:1052:15)
    at x.start (/Users/a/.vscode/extensions/betterthantomorrow.calva-2.0.452/node_modules/vscode-languageclient/lib/common/client.js:617:19)

Alexander Kouznetsov19:05:42

Running it directly results in: 

$ /Users/a/.vscode/extensions/betterthantomorrow.calva-2.0.452/clojure-lsp     
zsh: bad CPU type in executable: /Users/a/.vscode/extensions/betterthantomorrow.calva-2.0.452/clojure-lsp

Alexander Kouznetsov19:05:51

I have an Intel Mac

Alexander Kouznetsov19:05:00

I’m using nightly setting for the Clojure LSP in Calva.

Alexander Kouznetsov20:05:30

I’ve succeeded configuring Calva to use a version I installed via homebrew. Not sure what caused Calva built-in Clojure LSP to stop working. I also noticed that Calva doesn’t re-read Clojure LSP Path setting and I need to reload window each time I change it. cc @UKFSJSM38

pez06:05:21

I created an issue for the issue about the config not being re-read: https://github.com/BetterThanTomorrow/calva/issues/2557

Alexander Kouznetsov17:05:29

What about the bad CPU type in executable? Looks like Calva installs incorrect version of Clojure LSP - different platform.

ericdallo18:05:04

Weird, I think calva downloaded the wrong arch binary, but if we had a problem like that all macs of that type would be suffering of that, so must be some rare corner case

pez18:05:48

Yeah, I don’t know what to make of that one. Super weird. Thinking that maybe something went wrong with the download in some other way, causing a corrupt file and then the architecture check fails because of that.

1
Alexander Kouznetsov18:05:43

I still have that file around, I can check its checksum

👍 1
Alexander Kouznetsov18:05:30

Does calva use its own installation script that doesn’t check the checksum? I see that installation script in https://clojure-lsp.io/installation/ is doing that.

pez18:05:20

Calva doesn’t check it.

🙌 1
Alexander Kouznetsov18:05:56

Hmm, it looks like the checksums are not published.

Alexander Kouznetsov18:05:42

I’ll file a request to lsp to publish checksums and for calva to verify them 🙂

👍 1