Can you guys test this out? Thanks. I''ll make a real 4.3.1 release tomorrow.>From RubyGems.org: gem install --pre unicornChangeLog since v4.3.0: commit 4551c8ad4d63d4031c618f76d39532b39e88f9be Author: Eric Wong <normalperson at yhbt.net> Date: Fri Apr 27 14:42:38 2012 -0700 stream_input: call shutdown(2) if a client EOFs on us In case the Rack app forks before a client upload is complete, shutdown(2) the socket to ensure the client isn''t attempting to read from us (even if it explicitly stopped writes). commit 04901da5ae0b4655c83be05d24ae737f1b572002 Author: Eric Wong <normalperson at yhbt.net> Date: Fri Apr 27 11:48:16 2012 -0700 http_server: ignore ENOTCONN (mostly from shutdown(2)) Since there''s nothing unicorn can do to avoid this error on unconnected/halfway-connected clients, ignoring ENOTCONN is a safe bet. Rainbows! has long had this rescue as it called getpeername(2) on untrusted sockets --
On Fri, Apr 27, 2012 at 3:00 PM, Eric Wong <normalperson at yhbt.net> wrote:> Can you guys test this out? ?Thanks. ?I''ll make a real 4.3.1 release > tomorrow.Stopped the errors. Everything seems to be working fine here.
On Fri, Apr 27, 2012 at 6:07 PM, Matt Smith <matt at nearapogee.com> wrote:> On Fri, Apr 27, 2012 at 3:00 PM, Eric Wong <normalperson at yhbt.net> wrote: >> Can you guys test this out? ?Thanks. ?I''ll make a real 4.3.1 release >> tomorrow. > > Stopped the errors. Everything seems to be working fine here.Stopped the errors for me as well. -- Joel Nimety