This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-12
Channels
- # announcements (1)
- # babashka (32)
- # beginners (27)
- # calva (4)
- # clojure (18)
- # clojure-australia (2)
- # clojure-europe (11)
- # clojure-spec (8)
- # clojure-uk (15)
- # clojurescript (8)
- # cursive (14)
- # datomic (12)
- # fulcro (36)
- # graalvm (3)
- # graphql (2)
- # jobs (1)
- # meander (1)
- # pathom (5)
- # pedestal (12)
- # re-frame (1)
- # reagent (1)
- # reitit (2)
- # testing (12)
- # vim (2)
With VSpaceCode, I am excited to be giving Calva another whirl! (my poor old brain is very used to spacemacs key bindings).
Calva version 2.0.149 is out with the following fixes: • Fix: https://github.com/BetterThanTomorrow/calva/issues/933`${env:...}` • Update clojure-lsp to version 2021.01.12-02.18.26. Fix: https://github.com/BetterThanTomorrow/calva/issues/906
@borkdude In my testing of the above, I noticed the clj-kondo server was also orphaned / left running sometimes. It may be an even smaller chance with the kondo server, but see the fix here if you want to implement this fail-safe exit. https://github.com/clojure-lsp/clojure-lsp/pull/251/files
You can see more info about this https://github.com/microsoft/vscode-languageserver-node/issues/726#issuecomment-757687189, where it was explained that aside from a bug in vs code, servers should use the processId
in the initialize request to check if the parent process is alive, and exit if it's not.
@brandon.ringe Thanks a lot! Made an issue here: https://github.com/clj-kondo/clj-kondo.lsp/issues/14
