January 2025 - ruby-core - ml.ruby-lang.org

[ruby-core:120409] [Ruby master Feature#20982] Inconsistency between Hash#inspect and ENV.inspect in Ruby 3.4
by herwin (Herwin W) 14 Feb '25

14 Feb '25

Issue #20982 has been reported by herwin (Herwin W). ---------------------------------------- Feature #20982: Inconsistency between Hash#inspect and ENV.inspect in Ruby 3.4 https://bugs.ruby-lang.org/issues/20982 * Author: herwin (Herwin W) * Status: Open ---------------------------------------- Ruby 3.4 changed the stringified output of Hash to add whitespace to the hashrockets ``` ruby -e 'p({"a"=>"b"})' {"a" => "b"} ``` The output of `ENV.inspect` is very similar to `Hash#inspect`, but does not include the whitespace ``` ruby -e 'p ENV' {"SHELL"=>"/bin/bash", [...] } ``` Adding the extra whitespace around the hashrockets would improve the readability, and make things more consistent. -- https://bugs.ruby-lang.org/

2 3

[ruby-core:120787] [Ruby master Bug#21088] TCPSocket.new raises Socket::ResolutionError instead of Errno::ECONNREFUSED for hosts defined in /etc/hosts
by dmlary (David Lary) 14 Feb '25

14 Feb '25

Issue #21088 has been reported by dmlary (David Lary). ---------------------------------------- Bug #21088: TCPSocket.new raises Socket::ResolutionError instead of Errno::ECONNREFUSED for hosts defined in /etc/hosts https://bugs.ruby-lang.org/issues/21088 * Author: dmlary (David Lary) * Status: Open * ruby -v: 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- `TCPSocket.new` raises `Socket::ResolutionError` when the connection is refused for hosts defined in /etc/hosts. It should raise `Errno::ECONNREFUSED`. ```ruby [6] pry(main)> TCPSocket.new("test_system", 22) => #<TCPSocket:fd 8, AF_INET, 10.1.1.1, 51690> [7] pry(main)> TCPSocket.new("test_system", 12345) Socket::ResolutionError: getaddrinfo(3): No address associated with hostname (Socket::ResolutionError) [14] pry(main)> ::Socket.getaddrinfo("test_system", nil) => [["AF_INET", 0, "10.1.1.204", "10.1.1.204", 2 (0x2), 1 (0x1), 6 (0x6)], ["AF_INET", 0, "10.1.1.204", "10.1.1.204", 2 (0x2), 2 (0x2), 17 (0x11)], ["AF_INET", 0, "10.1.1.204", "10.1.1.204", 2 (0x2), 3 (0x3), 0]] ``` I've confirmed with tcpdump that the local system is sending the SYN to the remote host, and it is getting RST back. This was not a problem in 3.3.0. This does not happen when using `localhost` This does not happen for hosts resolvable via DNS. This is not the same as #20172 as this is a consistent failure and the fix for that was merged almost a year ago. -- https://bugs.ruby-lang.org/

7 8

[ruby-core:120851] [Ruby master Bug#21103] Binding problem with delegate methods
by tenderlovemaking (Aaron Patterson) 14 Feb '25

14 Feb '25

Issue #21103 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Bug #21103: Binding problem with delegate methods https://bugs.ruby-lang.org/issues/21103 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Assignee: tenderlovemaking (Aaron Patterson) * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ```ruby def foo(...) a = 123 binding.local_variable_get(:a) end p foo([]) ``` Expected output is `123`, actual output is some number. I think there is an off-by-one error in bindings created from delegate frames. -- https://bugs.ruby-lang.org/

3 2

[ruby-core:120807] [Ruby master Bug#21093] Backport patch for loongarch64 build
by hsbt (Hiroshi SHIBATA) 14 Feb '25

14 Feb '25

Issue #21093 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #21093: Backport patch for loongarch64 build https://bugs.ruby-lang.org/issues/21093 * Author: hsbt (Hiroshi SHIBATA) * Status: Closed * Assignee: naruse (Yui NARUSE) * Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED ---------------------------------------- https://github.com/ruby/ruby/pull/12653 -- https://bugs.ruby-lang.org/

2 1

[ruby-core:120674] [Ruby master Bug#21038] Preserve `errno` in `rb_fiber_scheduler_unblock`
by ioquatix (Samuel Williams) 14 Feb '25

14 Feb '25

Issue #21038 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #21038: Preserve `errno` in `rb_fiber_scheduler_unblock` https://bugs.ruby-lang.org/issues/21038 * Author: ioquatix (Samuel Williams) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- `rb_fiber_scheduler_unblock` can invoke user code that can affect `errno`, and at least in `io_binwrite`, this is unexpected. Whether `io_binwrite` should be fixed is a separate issue (it probably should be, as `errno` is not explicitly preserved or documented how it is preserved). See <https://github.com/socketry/io-event/issues/127> for more discussion. -- https://bugs.ruby-lang.org/

3 3

[ruby-core:120531] [Ruby master Bug#21012] Compiling `a['a','b'],=1` with parse.y fails
by tompng (tomoya ishida) 14 Feb '25

14 Feb '25

Issue #21012 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #21012: Compiling `a['a','b'],=1` with parse.y fails https://bugs.ruby-lang.org/issues/21012 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-06T01:50:53Z master c8e3d745fa) [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Compiling this code with parse.y fails with segmentation fault. ~~~ruby a['a','b'],=1 ~~~ Compiling `a['a',x],=1` generates instruction sequence that wrong contains `opt_aset_with`. ~~~ $ ruby --parser=parse.y --dump=insn -e "a['a',999],=1" == disasm: #<ISeq:<main>@-e:1 (1,0)-(1,13)> 0000 putself ( 1)[Li] 0001 opt_send_without_block <calldata!mid:a, argc:0, FCALL|VCALL|ARGS_SIMPLE> 0003 putobject_INT2FIX_1_ 0004 dup 0005 expandarray 1, 0 0008 topn 1001 .... 2006 topn 1001 2008 topn 1000 2010 opt_aset_with "a", <calldata!mid:[]=, argc:2, ARGS_SIMPLE> 2013 setn 1000 2015 pop .... 3014 pop 3015 leave ~~~ -- https://bugs.ruby-lang.org/

4 5

[ruby-core:120752] [Ruby master Bug#21085] [BUG] Stack consistency error with -ne
by segiddins (Samuel Giddins) 14 Feb '25

14 Feb '25

Issue #21085 has been reported by segiddins (Samuel Giddins). ---------------------------------------- Bug #21085: [BUG] Stack consistency error with -ne https://bugs.ruby-lang.org/issues/21085 * Author: segiddins (Samuel Giddins) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [arm64-darwin24] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Running the following crashes for me ``` shell echo '' | ruby -ne '' ``` Attached the diagnostic report as requested ---Files-------------------------------- ruby-2025-01-21-125203.ips (9.83 KB) -- https://bugs.ruby-lang.org/

4 4

[ruby-core:120713] [Ruby master Bug#21044] Prism maximum recursion depth is 1_000, parse.y is 10_000
by kddnewton (Kevin Newton) 14 Feb '25

14 Feb '25

Issue #21044 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Bug #21044: Prism maximum recursion depth is 1_000, parse.y is 10_000 https://bugs.ruby-lang.org/issues/21044 * Author: kddnewton (Kevin Newton) * Status: Open * Assignee: prism * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: REQUIRED ---------------------------------------- These should be aligned. This was because I misread the bison docs originally. Some folks are hitting this when trying to render Rails views too deeply. -- https://bugs.ruby-lang.org/

2 1

[ruby-core:120512] [Ruby master Bug#21008] Array#sum, Enumerator#sum, Numeric subclass
by MSP-Greg (Greg L) 14 Feb '25

14 Feb '25

Issue #21008 has been reported by MSP-Greg (Greg L). ---------------------------------------- Bug #21008: Array#sum, Enumerator#sum, Numeric subclass https://bugs.ruby-lang.org/issues/21008 * Author: MSP-Greg (Greg L) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-06T17:07:57Z master a61c16ba42) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The following code seems to show a bug or 'quirk'. When using a Numeric subclass, `Array#sum` works correctly, but `Enumerator#sum` does not. They both work fine when using a `Float`. ```ruby class Length < Numeric def initialize(val) @val = Float(val) end def to_f @val end end ary = [] #────────────────────────────────────────── Use Length ary[0] = Length.new 5 ary[1] = Length.new 10 ary[2] = Length.new 20 puts "Length ary #{ary.sum}" #=> 35.0 enum = ary.each puts "Length enum #{enum.sum}" #=> 20.0 #────────────────────────────────────────── Use Float ary[0] = 5.0 ary[1] = 10.0 ary[2] = 20.0 puts "Float ary #{ary.sum}" #=> 35.0 enum = ary.each puts "Float enum #{enum.sum}" #=> 35.0 ``` -- https://bugs.ruby-lang.org/

4 4

[ruby-core:120458] [Ruby master Misc#20995] exception escapes block given to IO.popen("-") in child process
by martin.dorey＠hds.com (Martin Dorey) 14 Feb '25

14 Feb '25

Issue #20995 has been reported by martin.dorey(a)hds.com (Martin Dorey). ---------------------------------------- Misc #20995: exception escapes block given to IO.popen("-") in child process https://bugs.ruby-lang.org/issues/20995 * Author: martin.dorey(a)hds.com (Martin Dorey) * Status: Open ---------------------------------------- I was surprised by the "ensure" being reached in the child process here: ``` ruby martind@stormy:~/tmp/D161730$ cat repro.rb #!/usr/bin/ruby -w parent = Process.pid() [false, true].each() { |nauseous| $stderr.puts("#{nauseous ? "" : "not "}raising exception from child:") begin IO.popen("-") { |io| unless io if nauseous raise("childish fit") end end } ensure $stderr.puts("in finalization block from #{Process.pid() == parent ? "parent" : "child"}") $stderr.puts() end } martind@stormy:~/tmp/D161730$ ~/download/ruby-3.3.4/ruby --version ruby 3.3.4 (2024-07-09 revision be1089c8ec) [x86_64-linux] martind@stormy:~/tmp/D161730$ ~/download/ruby-3.3.4/ruby -w repro.rb not raising exception from child: in finalization block from parent raising exception from child: in finalization block from child repro.rb:11:in `block (2 levels) in <main>': childish fit (RuntimeError) from repro.rb:7:in `popen' from repro.rb:7:in `block in <main>' from repro.rb:3:in `each' from repro.rb:3:in `<main>' in finalization block from parent martind@stormy:~/tmp/D161730$ ``` In the first iteration of the loop, we don't see the surprise - the child process exits when the block is completed. Only when an exception is thrown, in the second iteration, does the control flow escape from the block. It does so even for the SystemExit exception raised by exit(0) but not, as we see above, from just leaving the block (in which case perhaps we _exit(0) at https://github.com/ruby/ruby/blob/master/io.c#L8044) My expectation was that the block would be executed in the child process much like the "main" part of a program, with the usual unhandled exception reporting, which we see demonstrated above, being invoked as soon as the exception propagated out the block, rather than first unwinding the callers. I think the behavior is unchanged since the oldest version I was conveniently able to test, which was: ruby 1.8.7 (2012-02-08 patchlevel 358) [x86_64-linux] ... so I didn't file this report as a Bug in case users have (accidentally?) come to depend on the behavior. I didn't find any mention of this at eg https://ruby-doc.org/3.4.1/IO.html#method-c-popen but I didn't file this report as a Feature request for the documentation in case the documentation deliberately leaves open such possibilities. I didn't even find anyone else puzzling over this behavior on eg StackOverflow, but I felt that I should report it for the benefit of the next poor sap to run into it, especially in case that's Future Me. Could it be a case where a warning would be worth more than the trouble it causes? -- https://bugs.ruby-lang.org/

4 6