Thanks for the help with #33 @halorgium ... @bascule: looks like it was the known jRuby 1.7.3 fibers issue.
-
-
@bascule@halorgium er, safest. MisreadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@halorgium Moving to 1.7.2 at your recomm, trying to zero on on where rack.input is being missed or truncated for RackMultiparts.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@halorgium Without Celluloid.task_class in place now, workaround, reverting to 1.7.2 works. Magically fix #40 too? Damn! Nope -
@ofcourseiam@halorgium #40 looks legit bugged -
@bascule@halorgium Wow. Trying to resolve Reel#40 so far? Nothing but:http://www.youtube.com/watch?v=upWlI4VSHJw …
End of conversation
New conversation -
-
-
@halorgium@bascule Reel#40 is pretty well isolated. Any thoughts? If this can be resolved, I will move to Reel in production. -
@ofcourseiam@halorgium so you're fairly confident it's an encoding bug? -
@bascule@halorgium Fully sure. Duplicated w/ and w/o Rack. Used Rack::Request to extract multipart data. Encoding is off, in Reel's env(). -
@ofcourseiam@halorgium I guess my next question is whether or not http_parser.rb is implicated -
@bascule@halorgium I am looking into potential http_parser.rb complicity
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.