This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-29
Channels
- # announcements (7)
- # babashka (4)
- # beginners (21)
- # calva (31)
- # cljdoc (12)
- # cljsrn (5)
- # clojure (89)
- # clojure-europe (26)
- # clojurescript (9)
- # conjure (1)
- # cursive (3)
- # data-science (20)
- # events (2)
- # fulcro (4)
- # gratitude (7)
- # introduce-yourself (1)
- # lsp (24)
- # nextjournal (3)
- # off-topic (5)
- # re-frame (22)
- # shadow-cljs (48)
- # tools-deps (11)
I noticed recently that clojure-lsp
spends some time after startup analyzing something test related ("Refreshing testTree took 46.10 secs" etc). Is this something related to lsp-clojure-show-test-tree
?
and is this something that could be perhaps disabled with some configuration (assuming disabling it doesn't cripple anything critical)?
my motivation here is that loading a project already takes a considerable amount of time and if I can disable (or postpone) any expensive non-critical analysis with some config is great
I think there is no flag to disable that, but I'd be possible, but I don't think it waste too mamy resources, maybe you can profile or something
make test
is failing on master. java.lang.ClassNotFoundException: clojure_lsp.feature.test_tree.TestTreeParams
In the cli
tests. lib
tests are ok
Bisected to most recent commit: https://github.com/clojure-lsp/clojure-lsp/commit/bc7432048a2268e64111510ea6a694c06ab45f70
@UKFSJSM38 fighting with CI is always how you want to start your day, right?
@UKFSJSM38 new release seems good for me, happy to submit a nixpkgs pr if useful
thanks! that'd help a lot, you will probably just need to make some changes removing some datalevin code there
I think so, actually, feel free to remove all that code and just call the new make native-cli