This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-06
Channels
- # admin-announcements (1)
- # alda (2)
- # beginners (5)
- # boot (59)
- # clara (6)
- # cljs-dev (40)
- # cljsrn (32)
- # clojure (28)
- # clojure-austin (1)
- # clojure-belgium (67)
- # clojure-greece (60)
- # clojure-ireland (1)
- # clojure-japan (1)
- # clojure-russia (55)
- # clojure-spain (14)
- # clojure-spec (39)
- # clojure-uk (26)
- # clojurescript (152)
- # clojurewerkz (1)
- # cursive (21)
- # datomic (3)
- # dirac (15)
- # emacs (7)
- # events (2)
- # funcool (4)
- # hoplon (43)
- # immutant (1)
- # lambdaisland (1)
- # lein-figwheel (6)
- # leiningen (1)
- # off-topic (1)
- # om (23)
- # onyx (67)
- # other-languages (6)
- # pedestal (7)
- # planck (13)
- # proton (3)
- # protorepl (2)
- # re-frame (6)
- # reagent (5)
- # ring-swagger (6)
- # spacemacs (1)
- # specter (2)
- # yada (27)
@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.
@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:
curl -v -i -d @myfile -H "Content-Type: application/octet-stream"
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
My temp file is 47956 - it is always the Content-Length of the request
All works OK with this:
curl -v -i --data-binary @myfile -H "Content-Type: application/octet-stream"
@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?
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.
@malcolmsparks Thanks, I’ll check the points you raise.
@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.
@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
@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.
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
@stijn: https://facebook.github.io/react/blog/2015/10/19/reactiflux-is-moving-to-discord.html
@stijn: Check #C0CB40N8K particularly https://hackpad.com/Slackpocalypse-GRIaf1RgP5D
@stijn: I like http://matrix.org as an alternative. IRC, but federated logins and more extensible.
just to be clear, I'm not proposing shutting down this channel at all
Also, https://lobste.rs/s/gutv4l/introducing_yada and https://www.reddit.com/r/Clojure/comments/4mt4h1/introducing_yada/
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.