This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-28
Channels
- # announcements (5)
- # babashka (7)
- # beginners (46)
- # biff (28)
- # calva (7)
- # cider (3)
- # clerk (82)
- # clj-commons (9)
- # clj-kondo (7)
- # clojure (37)
- # clojure-dev (16)
- # clojure-europe (18)
- # clojure-norway (7)
- # clojurescript (8)
- # clojureverse-ops (3)
- # cursive (5)
- # datomic (4)
- # emacs (20)
- # exercism (2)
- # lsp (58)
- # off-topic (32)
- # polylith (11)
- # reitit (7)
- # tools-build (7)
- # xtdb (4)
I’m seeing a lot of errors like this. What could be causing them?
I think they happen each time the file is evaluated.
It appears like this and then “Go to output” button shows this long trace with some fail messages like the one above
Because there is a lot of stuff it is possible that I’m looking at the wrong one.
I think the question is better handled in #CPABC1H61. @UKFSJSM38 is there a possibility you would consider making clojure-lsp stop throwing those errors? VS Code pops them up in a very dramatic manner.

Thanks, I’ll continue the discussion there: https://clojurians.slack.com/archives/CPABC1H61/p1687979890280189.