This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-05
Channels
- # announcements (11)
- # architecture (22)
- # babashka (33)
- # beginners (15)
- # biff (8)
- # calva (7)
- # clj-otel (1)
- # cljs-dev (3)
- # cljsrn (5)
- # clojure (76)
- # clojure-art (1)
- # clojure-europe (36)
- # clojure-hamburg (3)
- # clojure-nl (1)
- # clojure-norway (7)
- # clojure-poland (12)
- # clojure-spec (2)
- # clojure-uk (7)
- # clojurescript (9)
- # cursive (22)
- # data-science (6)
- # datomic (7)
- # fulcro (9)
- # hoplon (14)
- # instaparse (2)
- # jobs-discuss (14)
- # london-clojurians (1)
- # matrix (32)
- # music (1)
- # nbb (8)
- # off-topic (18)
- # pathom (29)
- # pedestal (6)
- # portal (34)
- # reagent (2)
- # reitit (4)
- # releases (1)
- # sci (10)
- # shadow-cljs (7)
- # tools-deps (4)
- # vim (6)
When re-starting the VSC and starting the babashka repl I am getting these messages
[Error - 21:00:50] Connection to server got closed. Server will not be restarted.
[Error - 21:00:50] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 21:00:50] Clojure Language Client client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
Looks like clojure-lsp has troubles starting. Check if you can run it from the terminal. The binary is located in the Calva extension folder, which you can find using the VS Code command Extensions: Open Extensions Folder. Mine is here:
~/.vscode-insiders/extensions/betterthantomorrow.calva-2.0.369
❯ ls -lh clojure-lsp
-rwxrwxr-x 1 pez staff 106M Jun 3 11:40 clojure-lsp
Check if you can run it to report the version, for instance:
~/.vscode-insiders/extensions/betterthantomorrow.calva-2.0.369
❯ ./clojure-lsp --version
clojure-lsp 2023.05.04-19.52.47-nightly
clj-kondo 2023.04.15-SNAPSHOT
The “View: Show references” and “Calls: Show Call Hierarchy” commands aren’t working reliably anymore for me. They often show no results. Go to definition still works fine though. How can I diagnose the problem?
Can you confirm that clojure-lsp is running? Both those commands are provided by clojure-lsp, while Go to definition is primarily handled by the REPL.
Yes, a tooltip says “Clojure-lsp is active” at the bottom of the editor.