From: sam.saffron@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91611] [Ruby trunk Misc#15617] Any chance we can ship 2.5.4 sooner ratherthan later?
Date: Fri, 22 Feb 2019 22:54:29 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15617.20190222225422.ce32c36d956f6e2c@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15617.20190222225422@ruby-lang.org
Issue #15617 has been reported by sam.saffron (Sam Saffron).
----------------------------------------
Misc #15617: Any chance we can ship 2.5.4 sooner rather than later?
https://bugs.ruby-lang.org/issues/15617
* Author: sam.saffron (Sam Saffron)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
We started carrying code like this in Discourse due to #14634 breaking Queue after fork.
https://review.discourse.org/t/dev-disable-async-logging-in-development-on-broken-ruby/1829
I was wondering if there is any chance we can fast track a 2.5.4 release? This issue is quite severe cause there are quite a few forking web servers out there (puma and unicorn) so the failure mode is common in the wild.
#14634 is already backported
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-02-22 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15617.20190222225422@ruby-lang.org>
2019-02-22 22:54 ` sam.saffron [this message]
2019-02-26 17:58 ` [ruby-core:91625] [Ruby trunk Misc#15617] Any chance we can ship 2.5.4 sooner rather than later? shevegen
2019-03-05 3:06 ` [ruby-core:91668] " mike
2019-03-13 15:07 ` [ruby-core:91809] " nagachika00
2019-03-13 15:12 ` [ruby-core:91810] " nagachika00
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-15617.20190222225422.ce32c36d956f6e2c@ruby-lang.org \
--to=ruby-core@ruby-lang.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.
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).