unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <bofh@yhbt.net>
To: Jeremy Evans <code@jeremyevans.net>
Cc: unicorn-public@yhbt.net
Subject: Re: Rack 3 Compatibility
Date: Fri, 2 Jun 2023 00:27:04 +0000	[thread overview]
Message-ID: <20230602002704.M736062@dcvr> (raw)
In-Reply-To: <20230602000027.M794217@dcvr>

Eric Wong <bofh@yhbt.net> wrote:
> +++ b/lib/unicorn/socket_helper.rb
> @@ -15,6 +15,20 @@ def kgio_tryaccept # :nodoc:
>      end
>    end
> +  if IO.instance_method(:write).arity # Ruby <= 2.4

Erm, that should be:

	if IO.instance_method(:write).arity == 1 # Ruby <= 2.4

  reply	other threads:[~2023-06-02  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 18:54 Rack 3 Compatibility Jeremy Evans
2023-06-02  0:00 ` Eric Wong
2023-06-02  0:27   ` Eric Wong [this message]
2023-06-02  2:45   ` Jeremy Evans
2023-06-05  9:12     ` [PATCH v2] chunk unterminated HTTP/1.1 responses for Rack 3.1 Eric Wong

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:

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

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

  git send-email \
    --in-reply-to=20230602002704.M736062@dcvr \
    --to=bofh@yhbt.net \
    --cc=code@jeremyevans.net \
    --cc=unicorn-public@yhbt.net \


* 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


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).