This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-27
Channels
- # announcements (10)
- # aws (11)
- # beginners (158)
- # calva (8)
- # cider (14)
- # clj-kondo (1)
- # cljsrn (1)
- # clojure (83)
- # clojure-europe (5)
- # clojure-italy (25)
- # clojure-nl (3)
- # clojure-spec (12)
- # clojure-uk (20)
- # clojurescript (72)
- # community-development (18)
- # core-async (4)
- # core-logic (19)
- # cursive (11)
- # datomic (21)
- # duct (6)
- # events (1)
- # figwheel-main (3)
- # fulcro (15)
- # ghostwheel (1)
- # jobs (1)
- # leiningen (16)
- # off-topic (45)
- # onyx (3)
- # pathom (7)
- # perun (1)
- # ring (3)
- # shadow-cljs (48)
- # spacemacs (10)
- # specter (1)
- # sql (24)
- # tools-deps (7)
- # vscode (7)
- # xtdb (14)
@hiredman, Think I found the problem (though not the solution yet). I slowly added lines to my minimal example to figure out the offending line. It turned out to be a >!
where I put the result into another channel. This other channel interacts with a library I’m using. I know the library also makes use of async processes, maybe something could be interacting there?
I thought this could be related to some known bugs, the first two results of this quick search are interesting: https://clojure.atlassian.net/browse/ASYNC-223?jql=project%20%3D%20ASYNC%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22local%22%20ORDER%20BY%20priority%20DESC