This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-22
Channels
- # announcements (9)
- # beginners (96)
- # calva (14)
- # cider (49)
- # clj-kondo (29)
- # cljsrn (5)
- # clojure (55)
- # clojure-dev (37)
- # clojure-europe (4)
- # clojure-italy (4)
- # clojure-nl (5)
- # clojure-spec (5)
- # clojure-switzerland (3)
- # clojure-uk (5)
- # clojurescript (172)
- # cursive (14)
- # datomic (3)
- # duct (1)
- # emacs (6)
- # fulcro (17)
- # jobs (1)
- # leiningen (6)
- # nrepl (11)
- # off-topic (26)
- # pedestal (2)
- # re-frame (20)
- # reagent (9)
- # remote-jobs (3)
- # shadow-cljs (67)
- # spacemacs (24)
- # specter (6)
- # test-check (3)
- # tools-deps (18)
If I get back a message with printed-value
in it. Am I using some old nrepl stuff? I remember looking at this quite long ago and thought I learnt that that behaviour had been changed...
Also the out
message comes in a separate session than the eval
where I printed. And with an old id
. This is shadow-cljs which I start like so:
npx shadow-cljs -d cider/cider-nrepl:0.21.1 watch :app
I think piggieback still returns it in its responses. Or at least it did up to some version.
Does that mean that shadow is wrapping or threading it? Where should I be looking for a way to solve the problem, I guess I am asking. 😃
There was a bug in Figwheel for a while where it processed messages by taking an initial copy of the thread locals and processing them in a separate thread. This would cause the message id to be an older one, but a fixed older one.