This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-22
Channels
- # admin-announcements (7)
- # beginners (56)
- # boot (69)
- # cider (168)
- # cljs-dev (2)
- # clojure (170)
- # clojure-austin (25)
- # clojure-beijing (3)
- # clojure-belgium (2)
- # clojure-france (3)
- # clojure-poland (17)
- # clojure-russia (115)
- # clojure-uk (40)
- # clojurebridge (3)
- # clojurescript (87)
- # cursive (9)
- # datomic (30)
- # dirac (18)
- # editors (3)
- # emacs (14)
- # hoplon (195)
- # immutant (14)
- # jobs (3)
- # jobs-discuss (4)
- # leiningen (11)
- # melbourne (5)
- # mount (42)
- # off-topic (5)
- # om (24)
- # onyx (48)
- # parinfer (53)
- # proton (1)
- # protorepl (2)
- # re-frame (3)
- # reactive (2)
- # reagent (29)
- # rum (5)
- # spacemacs (4)
- # untangled (91)
- # yada (1)
@tcrawley: the issue states message sizes greater than 300k. I can see corruption for lower sizes too. Added some details of the exceptions I am seeing to the Undertow issue. https://issues.jboss.org/browse/UNDERTOW-684?focusedCommentId=13195644&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13195644 I dont know how you guys are setup, but in case you interact with Stuart Douglas (the resolver of the above issue), could you bring this to his notice. Thanks. And assuming the above issue covers the bugs I am seeing, when would Immutant pick up the Undertow version carrying the fix (1.4.0 i guess)?
@tcrawley: Stuart has seen my comment and says that his fix should cover the issues I am seeing.
@moizsj: once Stuart releases something with a fix (I suspect he'll put out a 1.3.x first), you can easily test it using a dep exclusion and a direct dep
if that works, we can update fairly quickly, assuming the new version doesn't cause any issues