@malcolmsparks: while porting to 1.1 we've come across a couple of places where we would like custom coercion... would you be happy with a pr to allow a custom coercer-fn to be specified on a resource ?

@mccraigmccraig: thanks for those reflogs, I'm looking into it now but will have more time this afternoon

on the custom coercer front, did you know you can provide your own defmethods? But that's app global - if you need on a resource-by-resource basis that makes sense too - yes, please send a PR

sorry for the brevity yesterday, was busy with stuff

np, brevity is functional

there's been some fixes to multipart recently, can you let me know the version/sha1 you're using?

we are now on 1.1.5

we were on 1.1.2, but i upgraded at some point last night and was still seeing the error on bigger files

is this your issue? https://github.com/juxt/yada/issues/86

yeah, that looks like it

the multipart upload code is a state machine, so it's pretty easy for fix once I find which state is wonky

i have a file that reliably causes it (given my browser etc) if that would be useful

having a repeatable test with data is very handy, in the past I've had a couple of reports that haven't been repeatable

yes - it would - very much - if you don't mind sending it to me