Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: mongrel-unicorn-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Cc: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: [ANN] unicorn 4.0.0.2.g19f7 prerelease
Date: Wed, 29 Jun 2011 07:29:36 +0000	[thread overview]
Message-ID: <20110629072936.GA10100@dcvr.yhbt.net> (raw)

I just pushed a prerelease gem to RubyGems.org with the following
changes.  Please let us know if there were any other regressions in
4.0.0.

Expect a final 4.0.1 release soonish...

Full git changelog (pushed to git://bogomips.org/unicorn.git):

commit 19f798301ac1884f423640efafb277b071bb5439
Author: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
Date:   Wed Jun 29 07:19:32 2011 +0000

    fix per-worker listen directive in after_fork hook
    
    The testcase for this was broken, too, so we didn't notice
    this :<
    
    Reported-by: ghazel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org on the Rainbows! mailing list,
    http://mid.gmane.org/BANLkTi=oQXK5Casq9SuGD3edeUrDPvRm3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

commit 38672501206c9e64d241e3d8571f70b198f0c1e5
Author: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
Date:   Mon Jun 27 20:51:16 2011 +0000

    configurator: truncate timeouts to 32-bit LONG_MAX
    
    IO.select in Ruby can't wait longer than this.  This
    means Unicorn can't support applications that take
    longer than 68 years to respond :(

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


                 reply	other threads:[~2011-06-29  7:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110629072936.GA10100@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=mongrel-unicorn-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).