This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-05
Channels
- # adventofcode (41)
- # bangalore-clj (4)
- # beginners (283)
- # boot (62)
- # clara (9)
- # cljsrn (3)
- # clojure (112)
- # clojure-brasil (1)
- # clojure-greece (1)
- # clojure-korea (6)
- # clojure-russia (99)
- # clojure-spec (29)
- # clojure-uk (12)
- # clojurescript (34)
- # clojurex (5)
- # core-logic (1)
- # cursive (31)
- # datomic (30)
- # devcards (5)
- # editors (19)
- # emacs (31)
- # events (5)
- # garden (4)
- # hoplon (137)
- # lein-figwheel (3)
- # luminus (4)
- # mount (7)
- # off-topic (7)
- # om (18)
- # om-next (3)
- # onyx (88)
- # proton (1)
- # protorepl (6)
- # re-frame (48)
- # reagent (15)
- # spacemacs (41)
- # testing (1)
- # untangled (2)
- # yada (18)
Yes, @dominicm might be right
(Ofc, he's very often right!)
I'll investigate but fighting my way into London so can't promise a fix... but here goes
@bbss I don't know if it's better, I like it better because I don't have to care 'how it is implemented' and it's clearer to me: netty waits-for-close; I don't have to wonder why there's a promise at that point in the code.
@kurt-yagram I like your solution. if netty crashed, I'd bet this would kill the process, allowing your process manager to at least restart.
@raymcdermott your stack trace is complaining about a function called populate-part
- I've just git grep'd the yada code-base and no function exists in yada called that
I know that yada is free of clojure.spec warnings since I use it a lot with clojure 1.9
I've just pushed an update to edge that updates to the latest dependencies of clojure 1.9, yada, bidi and aero.
It's coming from aleph, @raymcdermott possibly your yada/aleph is out of date, I do remember there being a spec problem with aleph.
@raymcdermott @dominicm - yes, yada doesn't depend on the spec-happy version of aleph yet - yada is marked 'stable', it wouldn't be right to depend on a version of aleph that Zach has explicitly labelled 'alpha'
edge, on the other hand, makes no such claims to stability, it's not called 'bleeding edge' for nothing
thanks @malcolmsparks @dominicm. I figured it was coming from further down the stack. FYI I did take the versions from edge when I first started and bumped into some compatibility issues immediately so backed off to the stable versions. Now I am a little more comfortable with yada I am willing to experiment a little more...