Fork me on GitHub
#yada
<
2016-06-06
>
malcolmsparks07:06:24

@mark.melling: Hi Mark - I've been able to replicate what youre seeing - this has been a netty issue that went away and is now back. I need to investigate further.

malcolmsparks08:06:09

@mark.melling: I spoke to soon, it seems to be working as expected but I have noticed something very peculiar with curl. I am doing this:

malcolmsparks08:06:04

curl  -v -i -d @myfile  -H "Content-Type: application/octet-stream"

malcolmsparks08:06:59

It seems curl is setting the Content-Length header in the request to 47956 (in my case) where the file myfile is 95770 bytes long

malcolmsparks08:06:21

My temp file is 47956 - it is always the Content-Length of the request

malcolmsparks08:06:04

All works OK with this:

curl  -v -i --data-binary @myfile  -H "Content-Type: application/octet-stream"

malcolmsparks08:06:52

@mark.melling: In summary, I was wrong about being able to replicate the issue (I was using curl wrong). Can you explain a bit more about what you tried with your audio files? Was your client using Transfer Encoding or was the Content-Length header set?

malcolmsparks08:06:57

Also, please check that you're using [aleph "0.4.1"] and [io.netty/netty-all "4.1.0.CR3"] (which it depends on). There's been some problems with other versions - check your lein deps :tree to ensure you weren't bringing in other dependencies.

mark.melling08:06:25

@malcolmsparks Thanks, I’ll check the points you raise.

malcolmsparks08:06:47

@mark.melling: Thanks - there could still be some underlying issues here still with aleph/netty - this has been problematic in the past and I've even got a half-complete implementation of yada on RedHat's undertow server to diagnose whether these issues are bugs in yada or further down the stack. The rest of yada is pretty solid but this particular area (uploads of large bodies) has smoked out a few issues in underlying components.

mark.melling09:06:08

@malcolmsparks: Sorry! It looks like there isn’t a problem, and like you I’d fallen foul of not using curl correctly, specifying -d rather than —data-binary

malcolmsparks10:06:00

@mark.melling: yes - that's a strange curl 'feature' I hadn't come across 🙂 Anyway, it's was good for me to revisit that part of the code-base so no problem.

malcolmsparks10:06:13

to everyone on the #C0702A7SB channel, I'm also monitoring https://gitter.im/juxt/yada - there is some uncertainty about slack's future support for large communities and this is a hedge against the service being shut-down

stijn11:06:35

ok, any reference to slack not supporting these communities anymore?

stijn12:06:29

after all irc wasn't too bad 🙂

dominicm12:06:23

@stijn: I like http://matrix.org as an alternative. IRC, but federated logins and more extensible.

malcolmsparks12:06:19

just to be clear, I'm not proposing shutting down this channel at all

dominicm12:06:27

Long live #C0702A7SB

stijn12:06:10

matrix looks nice. didn't know about that

stijn12:06:40

interesting concept

thomas15:06:35

yadarians
Love it!!!

malcolmsparks16:06:50

I should have mentioned, another plus with gitter is permanent histories which means if there's any useful discussions there then they'll be permanent and I'll link to them from here.