[#41431] [ruby-trunk - Bug #5694][Open] Proc#arity doesn't take optional arguments into account. — Marc-Andre Lafortune <ruby-core@...>

27 messages 2011/12/01
[#41442] [ruby-trunk - Bug #5694] Proc#arity doesn't take optional arguments into account. — Thomas Sawyer <transfire@...> 2011/12/01

[#41443] Re: [ruby-trunk - Bug #5694] Proc#arity doesn't take optional arguments into account. — Yehuda Katz <wycats@...> 2011/12/01

Maybe we can add a new arity_range method that does this?

[#41496] [ruby-trunk - Bug #5714][Open] Unexpected error of STDIN#read with non-ascii input on Windows XP — Heesob Park <phasis@...>

22 messages 2011/12/06

[#41511] [ruby-trunk - Bug #5719][Open] Hash::[] can't handle 100000+ args — Nick Quaranto <nick@...>

13 messages 2011/12/07

[#41557] [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong — Yukihiro Matsumoto <matz@...>

14 messages 2011/12/08

[#41586] [ruby-trunk - Feature #5741][Open] Secure Erasure of Passwords — Martin Bosslet <Martin.Bosslet@...>

17 messages 2011/12/10

[#41672] [ruby-trunk - Feature #5767][Open] Cache expanded_load_path to reduce startup time — Yura Sokolov <funny.falcon@...>

13 messages 2011/12/15

[#41681] Documentation of the language itself (syntax, meanings, etc) — Rodrigo Rosenfeld Rosas <rr.rosas@...>

Since Ruby is built on top of simple concepts, most of the documentation

23 messages 2011/12/15
[#41683] Re: Documentation of the language itself (syntax, meanings, etc) — Gary Wright <gwtmp01@...> 2011/12/15

[#41686] Re: Documentation of the language itself (syntax, meanings, etc) — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2011/12/16

Em 15-12-2011 19:23, Gary Wright escreveu:

[#41717] Feature : optional argument in File.join — Michel Demazure <michel@...>

In Windows, when using File.join, one often ends with a path containing

13 messages 2011/12/19
[#41719] Re: Feature : optional argument in File.join — Luis Lavena <luislavena@...> 2011/12/19

On Mon, Dec 19, 2011 at 6:09 AM, Michel Demazure <michel@demazure.com> wrot=

[#41720] Re: Feature : optional argument in File.join — Michel Demazure <michel@...> 2011/12/19

Luis Lavena wrote in post #1037331:

[#41728] [ruby-trunk - Feature #5781][Open] Query attributes (attribute methods ending in `?` mark) — Thomas Sawyer <transfire@...>

15 messages 2011/12/19

[#41799] Best way to separate implementation specific code? — Luis Lavena <luislavena@...>

Hello,

15 messages 2011/12/24
[#41800] Re: Best way to separate implementation specific code? — KOSAKI Motohiro <kosaki.motohiro@...> 2011/12/24

2011/12/24 Luis Lavena <luislavena@gmail.com>:

[#41811] Re: Best way to separate implementation specific code? — "U.Nakamura" <usa@...> 2011/12/26

Hello,

[#41817] Re: Best way to separate implementation specific code? — Luis Lavena <luislavena@...> 2011/12/26

On Sun, Dec 25, 2011 at 10:51 PM, U.Nakamura <usa@garbagecollect.jp> wrote:

[#41812] [ruby-trunk - Feature #5809][Open] Benchmark#bm: remove the label_width parameter — Benoit Daloze <redmine@...>

11 messages 2011/12/26

[ruby-core:41555] [Backport93 - Backport #5723] Ruby fails when standard input is closed

From: Randal Moore <rdmoore@...>
Date: 2011-12-08 20:53:50 UTC
List: ruby-core #41555
Issue #5723 has been updated by Randal Moore.


Ruby is being forked as a subprocess by a service which runs on both windows and linux.  With ruby 1.8, a closed STDIN worked and was portable to both platforms.  As a work-around, we are in the middle of switching to using NULL on Windows and /dev/null on Linux.  This will likely be a better long term solution for our service, as other programs are also unhappy with closed STDIN.

We expect our work-around will work, so this issue is low priority.  Just thought someone could look into the regression.

Thanks
----------------------------------------
Backport #5723: Ruby fails when standard input is closed  
http://redmine.ruby-lang.org/issues/5723

Author: Randal Moore
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


If the ruby process is launched with its standard input closed, it does not behave very well.  The following output was logged by the ruby process under these circumstances.  The attached source file can be used to produce a minimal executable that duplicates the issue.  Note that this appears to be something that changed between 1.9.2 and 1.9.3.

[BUG] rb_update_max_fd: invalid fd (0) given.
ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]

-- Control frame information -----------------------------------------------
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP


-- C level backtrace information -------------------------------------------
-e [0x8173762]
-e [0x81b7de8]
-e(rb_bug+0x35) [0x81b7e85]
-e [0x8073427]
-e [0x8079be0]
-e [0x806da5a]
-e(ruby_init+0x97) [0x805b317]
-e [0x8058887]
/lib/libc.so.6(__libc_start_main+0xdc) [0x3cedec]
-e [0x8058781]

-- Other runtime information -----------------------------------------------

0: can't convert false into String (TypeError)



-- 
http://redmine.ruby-lang.org

In This Thread