This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-20
Channels
- # aleph (1)
- # announcements (1)
- # aws (11)
- # babashka (117)
- # beginners (34)
- # calva (13)
- # cider (3)
- # clj-commons (8)
- # clj-kondo (24)
- # clj-yaml (36)
- # cljsrn (46)
- # clojure (50)
- # clojure-australia (5)
- # clojure-europe (239)
- # clojure-nl (3)
- # clojure-norway (3)
- # clojure-spec (16)
- # clojurescript (25)
- # core-typed (20)
- # cursive (41)
- # datahike (1)
- # datalevin (1)
- # datomic (17)
- # fulcro (27)
- # hyperfiddle (35)
- # introduce-yourself (1)
- # jobs (4)
- # lsp (20)
- # malli (8)
- # meander (8)
- # nbb (1)
- # off-topic (31)
- # parinfer (9)
- # pathom (3)
- # portal (2)
- # re-frame (20)
- # react (2)
- # reagent (8)
- # releases (1)
- # remote-jobs (4)
- # scittle (2)
- # shadow-cljs (8)
- # slack-help (4)
- # sql (30)
- # squint (3)
- # tools-deps (34)
- # xtdb (21)
Hi everybody! I'm missing some printlns in my multithreaded application and trying to make everything to use the same PrintWriter I see cider nrepl is returning a different PrintWriter in *out*
every time I call it, which is different from the clj repl behavior.
user> *out*
#object[java.io.PrintWriter 0xfd3434c "java.io.PrintWriter@fd3434c"]
user> *out*
#object[java.io.PrintWriter 0x2229c88a "java.io.PrintWriter@2229c88a"]
user> *out*
#object[java.io.PrintWriter 0x1a8cdc5e "java.io.PrintWriter@1a8cdc5e"]
Is this because the nrepl server is creating a new PrintWriter for every request? what is the correct way of using printlns in cider repl without missing some printlns outputs?