This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-04
Channels
- # aleph (1)
- # asami (6)
- # babashka (44)
- # beginners (20)
- # calva (6)
- # circleci (1)
- # clj-kondo (2)
- # cljdoc (2)
- # clojure (184)
- # clojure-europe (13)
- # clojure-nl (4)
- # clojure-spain (1)
- # clojure-uk (4)
- # clojurescript (35)
- # code-reviews (1)
- # conjure (3)
- # core-async (60)
- # core-logic (1)
- # cursive (11)
- # data-science (2)
- # events (11)
- # graalvm (4)
- # graphql (2)
- # introduce-yourself (1)
- # jobs (2)
- # leiningen (3)
- # malli (16)
- # minecraft (6)
- # practicalli (1)
- # reagent (3)
- # reitit (1)
- # releases (3)
- # remote-jobs (2)
- # rewrite-clj (21)
- # shadow-cljs (12)
- # tools-deps (21)
- # vim (16)
I found a bug in my code on dev earlier - if a test errors, and the “error” message from cider-nrepl has no line number data, the output pane will show incomplete data. I’ll PR a fix tomorrow.
This is a strange issue - sometimes the output window does not get the prompt appended after a test run, and other times it does. When I run the same test over and over, it works sometimes and doesn’t work other times.
It works consistently when I trigger the test with the c t keybinding, but when I click on the “run test” in the UI it fails. So triggering from the Test Explorer UI must behave a little differently.
Now that the feature is released, we should file an issue about this strangety. Can you do it, since you know most about it.
Will do. 👍