This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-18
Channels
- # beginners (123)
- # boot (3)
- # cider (6)
- # clara (1)
- # cljs-dev (139)
- # cljsrn (9)
- # clojure (59)
- # clojure-italy (5)
- # clojure-uk (41)
- # clojured (10)
- # clojurescript (67)
- # community-development (1)
- # component (2)
- # core-async (7)
- # cursive (4)
- # datomic (4)
- # defnpodcast (2)
- # fulcro (23)
- # graphql (1)
- # jobs (2)
- # leiningen (4)
- # off-topic (32)
- # portkey (7)
- # protorepl (5)
- # re-frame (19)
- # reagent (5)
- # reitit (23)
- # shadow-cljs (29)
- # slack-help (1)
- # spacemacs (1)
- # tools-deps (21)
- # unrepl (18)
I’ve got a strange issue with core.async where using timeout
deep inside an async process causes core.async to lock up completely. I’ve posted a more in depth question & sample code over the https://clojureverse.org/t/core-async-locks-up-when-using-timeout-deep-inside-async-processes/1780 and would love to understand what on earth is going wrong
@kennethkalmer I'm not that familiar with transducers, but it's sortof like a more powerful reducer? On line 23, is this result being passed back into process-n
?
which might make it look like it's locking up, because the timeout hits >1s after only 10 iterations, not sure if this is the case
the values will always be < 10, so the timeout will be up to 1s max
calling (process-n 10)
by itself will take 1s, but when (process-n 10)
is called inside (async/pipeline)
it just blocks, but with (async/pipeline-blocking)
it seems to work
however, that means my example no longer matches the issue I’m experiencing in my code