Afraid of leaks with async chan

I'm a bit unsure of which channels will be collected and which will remain and potentially result in an out of memory error. I'd like to understand when I should close, unsub and untap channels to avoid leaks. It feels like a very difficult task to verify there are no leaks. For example: (defn

Re: About determinism of async

t; On Wed, Oct 11, 2017 at 6:09 AM, Gary Trakhman > wrote: > >> If you don't want to split at the consumer I would recommend adding >> another channel, and piping it with a cat xform as mentioned above. >> >> On Oct 11, 2017 3:28 AM, "JokkeB" > >&g

Re: About determinism of async

they're one thing. `(partition-all 2)` will return a >> transducer xform that chunks up your message stream by 2 >> https://clojuredocs.org/clojure.core/partition-all, and if you need to >> undo it you can do so with the `cat` transducer >> https://clojuredocs.org/clojure.core/

Re: About determinism of async

partition? > > On Tue, Oct 10, 2017 at 10:30 AM JokkeB > > wrote: > >> I'm wondering about a case when using async: >> >> I have a channel where I write from multiple threads. One of the sources >> is a go-loop with a timeout, so each second I write someth

About determinism of async

I'm wondering about a case when using async: I have a channel where I write from multiple threads. One of the sources is a go-loop with a timeout, so each second I write something to the channel. If I do two consecutive writes inside the go block, can another thread write between the two writes

Re: Application silently shuts down by itself after running for some hours

different topic. Thanks again! perjantai 3. maaliskuuta 2017 17.57.20 UTC+2 JokkeB kirjoitti: > > I have an application which I run with "lein run". The main looks > something like this > > (defn -main [] > (log/info "start") > (log/info "channel ret

Re: Application silently shuts down by itself after running for some hours

After adding this, I still can't see an exception before the app dies. maanantai 6. maaliskuuta 2017 12.04.16 UTC+2 JokkeB kirjoitti: > > Thanks for the reply. > > I haven't tried catching any or all errors. Is it a false assumption that > an error should be logged

Re: Application silently shuts down by itself after running for some hours

across this similar post > <https://groups.google.com/forum/#!msg/clojure/xlbjGGk8qsY/m1fbElGT3PsJ> > from a few years ago... not sure if it will help, but it may. > > > On Friday, March 3, 2017 at 10:57:20 AM UTC-5, JokkeB wrote: >> >> I have an application which I run

Application silently shuts down by itself after running for some hours

I have an application which I run with "lein run". The main looks something like this (defn -main [] (log/info "start") (log/info "channel returned" (async/http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" grou

Re: Why doesn't reduce return a transducer

kground thread pump numbers in > (future (a/onto-chan ch (range 6))) > > ;; drain results > ( ;;=> [0 1 3 6 10 15] > > > > On Wednesday, August 10, 2016 at 8:26:39 AM UTC-5, JokkeB wrote: >> >> Hi, >> >> I'm wondering why reduce doesn't

Why doesn't reduce return a transducer

Hi, I'm wondering why reduce doesn't return a transducer like map does. For example I'd like to this: (async/chan 1 (reduce +)) I could use async/reduce but it doesn't provide a result before the source channel closes, I want to have a streaming result. What is the philosophy behind not havin