This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-14
Channels
- # adventofcode (62)
- # beginners (78)
- # boot (26)
- # boot-dev (9)
- # cider (73)
- # cljs-dev (33)
- # cljsrn (36)
- # clojure (159)
- # clojure-android (1)
- # clojure-austin (1)
- # clojure-greece (79)
- # clojure-italy (10)
- # clojure-nl (3)
- # clojure-russia (11)
- # clojure-spec (33)
- # clojure-uk (26)
- # clojurescript (107)
- # core-async (22)
- # core-logic (12)
- # cursive (16)
- # datomic (13)
- # devcards (5)
- # duct (36)
- # emacs (4)
- # figwheel (3)
- # fulcro (107)
- # graphql (171)
- # hoplon (27)
- # instaparse (24)
- # jobs-discuss (34)
- # juxt (3)
- # lein-figwheel (1)
- # leiningen (8)
- # lumo (11)
- # off-topic (9)
- # onyx (79)
- # parinfer (1)
- # pedestal (75)
- # re-frame (27)
- # rum (1)
- # shadow-cljs (11)
- # spacemacs (20)
- # specter (17)
- # unrepl (96)
So i'm running into a weird issue where if i build an uberjar with lein my (mult (chan 16)) doesn't seem to be getting messages. If i build it via mvn with a pom created by lein pom or if i'm using the repl it seems to work fine. Has anyone seen anything like this?
lein -version Leiningen 2.7.0 on Java 1.8.0_74 Java HotSpot(TM) 64-Bit Server VM mvn -version Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T09:41:47-07:00) Java version: 1.8.0_74, vendor: Oracle Corporation
i've also tried building it via: lein -version Leiningen 2.7.0 on Java 1.8.0_121 OpenJDK 64-Bit Server VM
I have a transducer that should pick it ups and set a watched variable. I'm not getting any changes on the watched var and I've added a log to the transducer which isn't outputting anything either. It is if i am in the repl however or using a mvn build
yeah i'm adding my transducer like this so it should constantly be being consumed. (defn add-listening-transducer [mult-chan fx] (sink (add-transducer (tap mult-chan (chan 16)) fx)))
when a channel is created with a transducer, that transducer isn't consuming from the channel, it is operating on values that pass through the channel
yeah - that would readily explain core.async stalling to a complete halt
I can fix that. it hasn't been a problem still not sure why the two different builds act differently
I ignored the build stuff because in my experience most people's builds are tire fires, so more signal than noise