Fork me on GitHub
#yada
<
2016-12-05
>
dominicm08:12:29

Edge is at alpha12, very possible 14 has a new spec which is catching out yada

malcolmsparks08:12:11

Yes, @dominicm might be right

malcolmsparks08:12:27

(Ofc, he's very often right!)

malcolmsparks08:12:30

I'll investigate but fighting my way into London so can't promise a fix... but here goes

kurt-yagram08:12:16

@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.

dominicm08:12:33

@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.

dominicm08:12:46

But as you said, harder as it exposes the underneath of yada

malcolmsparks08:12:37

@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

malcolmsparks08:12:25

I know that yada is free of clojure.spec warnings since I use it a lot with clojure 1.9

malcolmsparks08:12:03

I've just pushed an update to edge that updates to the latest dependencies of clojure 1.9, yada, bidi and aero.

dominicm08:12:36

It's coming from aleph, @raymcdermott possibly your yada/aleph is out of date, I do remember there being a spec problem with aleph.

malcolmsparks08:12:24

@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'

malcolmsparks08:12:00

edge, on the other hand, makes no such claims to stability, it's not called 'bleeding edge' for nothing

raymcdermott09:12:13

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...

raymcdermott12:12:44

I am not using boot in my project (I know I’m uncool) and also not using as many dependencies as edge

raymcdermott12:12:15

i’m having trouble with ring-swagger failing specs on REPL start up

raymcdermott12:12:16

also I see that there are two versions of [prismatic/schema “1.1.3”] and [prismatic/schema “1.0.4”] which is confusing me