I think the nightly build of LSP might be broken? I just fired up VS Code/Calva (with the LSP version set to nightly) and got an ENOENT failed to spawn error. I set it back to latest and restarted VS Code/Calva and that version works fine.

I still don't see any import related code actions. I've been wondering if it could be due to my version of JDK ?

Released clojure-lsp https://github.com/clojure-lsp/clojure-lsp/releases/tag/2023.08.06-00.28.06 with lots of fixes and memory usage improvements The jvm version now should not throw OutOfMemory exceptiosn when saving the cache on huge projects :) • General ◦ Fix truncation of namespaced keywords https://github.com/clojure-lsp/clojure-lsp/pull/1640 ◦ Add rewrite-clj node to cursor-info. ◦ Fixing semantic-tokens, collons not managed by lsp anymore. https://github.com/clojure-lsp/clojure-lsp/issues/1550 ◦ Fix :paths-ignore-regex setting to consider settings reload. ◦ Bump clj-kondo to 2023.07.14-20230717.090255-3. https://github.com/clojure-lsp/clojure-lsp/issues/1624 ◦ Fix inconsistencies with :defined-by->lint-as. ◦ Improve memory usage during cache save, avoiding "Out of memory" exceptions. ◦ Prevent file rename when a namespace is defined in multiple files https://github.com/clojure-lsp/clojure-lsp/issues/1574 ◦ Fix user formatting setting being override by :style/indent metadata in macros. ◦ Bump cljfmt to 0.11.2. https://github.com/clojure-lsp/clojure-lsp/issues/1634 ◦ Bump lsp4clj to 1.8.1. • Editor ◦ Avoid returning all known keywords on empty keywords completion for performance reasons. • API/CLI ◦ Improve mem/cpu usage using less analysis for tasks.