mccraigmccraig of the clan mccraig

on the positive side, i didn't encounter this in real-life code... i was looking for another bug and was getting behaviour which was dependent on some property of Deferreds and...

i'm currently having some issues with error propagation - in particular i'd like to be able to have errors which happen during a `map` thrown when a `reduce` finally happens....

set `{:raw-stream? true}` on your `aleph.http/start-server` opts and this problem goes away https://github.com/ztellman/aleph/blob/master/src/aleph/http.clj#L32 and it only took about 18h of furious debugging to figure this out

yep, that's what this commit i did while debugging prevents (and thus reveals the underlying exception) https://github.com/juxt/yada/commit/63872b9eb78136cb9a62e3c9640952b1b3c8443a

i was just bitten badly by context management (made worse by the renaming of cats -> funcool/cats, and transitive deps causing 2 conflicting versions of cats being loaded unbeknownst to...

i took a basic reagent-template app and modified it to work with aleph/manifold... which probably satisfies the same itch you are looking for http-kit to scratch (async, websockets) ? https://github.com/mccraigmccraig/sparky-elephants...

hmm, iirc i had problems with ring.middleware.reload not re-creating the handler chain, so i modified ring.middleware.reload ( https://github.com/mccraigmccraig/sparky-elephants/blob/master/env/dev/clj/sparky_elephants/wrap_reload.clj ) and then recreate the handler chain on each request

anyway, sounds like you don't need any help with aleph ;)

if you would take a PR, i could do an aleph profile in the next few weeks ?

cool, i'll get on it when i have a moment :)