This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-03
Channels
- # aleph (3)
- # beginners (139)
- # boot (3)
- # cider (12)
- # cljs-dev (18)
- # clojure (100)
- # clojure-dev (21)
- # clojure-dusseldorf (5)
- # clojure-germany (1)
- # clojure-italy (35)
- # clojure-nl (26)
- # clojure-spec (4)
- # clojure-uk (60)
- # clojurescript (11)
- # clojutre (4)
- # cursive (21)
- # data-science (21)
- # datomic (47)
- # editors (3)
- # emacs (2)
- # events (4)
- # figwheel (2)
- # fulcro (28)
- # jobs (27)
- # jobs-discuss (21)
- # lein-figwheel (3)
- # midje (2)
- # off-topic (20)
- # om-next (4)
- # onyx (10)
- # overtone (1)
- # pedestal (2)
- # portkey (14)
- # re-frame (71)
- # reagent (44)
- # reitit (11)
- # remote-jobs (1)
- # ring-swagger (4)
- # shadow-cljs (64)
- # spacemacs (11)
- # testing (2)
- # tools-deps (8)
- # vim (8)
aleph appears to acquire from a pool here : https://github.com/ztellman/aleph/blob/master/src/aleph/flow.clj#L78 , which is using the callback mechanism to fulfil a Deferred
... presumably the callback mechanism is to allow for the case where a pool has already reached its maximum size and .acquire
requests are then queued
without having traced the code all the way, that's what appears to be happening here : https://github.com/ztellman/dirigiste/blob/master/src/io/aleph/dirigiste/Pool.java#L409
i need to look at the aleph client some more... i've had a bug recently where the aleph client appears to stop working, although everything else carries on working fine... my guess was that aleph was leaking connections causing a terminal pause here: https://github.com/ztellman/aleph/blob/master/src/aleph/http.clj#L261 , but i've not managed to duplicate the bug in a test environment yet