Ruby Issue Tracking System

04/23/2018

05:54 AM Ruby trunk Revision 63245 (trunk): test/ruby/test_io.rb: add extra Thread#join to delay close

Maybe this fixes some CI failures. Also, use different timeouts
for each item for hopefully easier diagnosis.

04/22/2018

10:21 PM Ruby trunk Feature #14705 (Open): [PATCH] eval.c (ruby_setup): disable THP on Linux

Transparent Huge Pages (THP) decrease the effectiveness of
CoW-friendly GC because it decreases page granularity. T...

09:21 PM Ruby trunk Feature #14703 (Closed): [PATCH] net/imap: set SO_KEEPALIVE on TCP sockets

Applied in changeset trunk|r63243.
----------
net/imap: set SO_KEEPALIVE on TCP sockets
Otherwise connections (comm...

09:21 PM Ruby trunk Revision 63243 (trunk): net/imap: set SO_KEEPALIVE on TCP sockets

Otherwise connections (commonly on IDLE, but it could be any
command) may never receive notifications of link errors....

12:09 PM Ruby trunk Misc #14497 (Closed): [PATCH] thread*: all condvars are monotonic

Applied in changeset trunk|r63238.
----------
thread*: all condvars are monotonic
There's no reason to use CLOCK_RE...

12:09 PM Ruby trunk Revision 63238 (trunk): thread*: all condvars are monotonic

There's no reason to use CLOCK_REALTIME for any condvars in Ruby.
Indeed, we initialized all condvars with RB_CONDATT...

12:12 AM Ruby trunk Bug #14681: `syswrite': stream closed in another thread (IOError)

samuel@oriontransfer.org wrote:
> > We no longer set O_NONBLOCK on sockets/pipes by default since
> > 1.9+; and bu...

04/21/2018

11:32 PM Ruby trunk Revision 63231 (trunk): test/ruby/test_io.rb: try to diagnose stuck test_recycled_fd_close

I can't reproduce the problem myself, but gets loop seems ought
to give more useful information for tracking down whe...

06:12 PM Ruby trunk Bug #14681: `syswrite': stream closed in another thread (IOError)

samuel@oriontransfer.org wrote:
> I reviewed your suggestion, and while it (in theory) works
> with the original e...

06:03 PM Ruby trunk Bug #14681: `syswrite': stream closed in another thread (IOError)

samuel@oriontransfer.org wrote:
> Excuse my ignorance, but if you call write, why can't you just
> directly invoke...