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

[ruby-core:120335] [Ruby master Feature#20971] Deprecate `rb_path_check`
by Earlopain (Earlopain _) 14 Feb '25

14 Feb '25

Issue #20971 has been reported by Earlopain (Earlopain _). ---------------------------------------- Feature #20971: Deprecate `rb_path_check` https://bugs.ruby-lang.org/issues/20971 * Author: Earlopain (Earlopain _) * Status: Open ---------------------------------------- With #16131, various code around $SAFE, taint, etc. has been deprecated and removed. GH PR https://github.com/ruby/ruby/pull/2476. Now, [`rb_path_check`] still exists as part of the public API, with Ruby itself never using or testing it. I believe it should have been deprecated and was simply missed. Should it be deprecated today or is that not worth the effort? Docs for it are pretty vague: https://github.com/ruby/ruby/blob/33f95d632dce42fac35da29eaed33f0a5a4f0dcb/… > This function is mysterious. What it does is not immediately obvious. Also what it does seems platform dependent. [`rb_path_check`]: https://github.com/ruby/ruby/blob/33f95d632dce42fac35da29eaed33f0a5a4f0dcb/… -- https://bugs.ruby-lang.org/

5 12

[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:120882] [Ruby master Bug#21114] Prism hangs up while parsing deeply nested `def`
by tompng (tomoya ishida) 14 Feb '25

14 Feb '25

Issue #21114 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #21114: Prism hangs up while parsing deeply nested `def` https://bugs.ruby-lang.org/issues/21114 * Author: tompng (tomoya ishida) * Status: Open * Assignee: prism * ruby -v: ruby 3.5.0dev (2025-02-05T08:15:30Z master 141f2924ee) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ~~~ruby Prism.parse "def f\n" * 500 # Ruby 3.4 Prism.parse "def f\n" * 5000 # Ruby 3.5 Prism.parse "def initialize: ()->void\n" * 250 # Ruby 3.4 Prism.parse "def initialize: ()->void\n" * 2500 # Ruby 3.5 #=> hang up, Ctrl-C doesn't work ~~~ Expect to raise ParseError with `@type=:nesting_too_deep` like `Prism.parse '(1+'*10000` ### Background Runnning `rdoc` in `ruby/rbs` directory with Ruby 3.4, RDoc hangs up. RDoc tries to parse the partial file content, and stops with `stdlib/ripper/0/ripper.rbs` (https://github.com/ruby/rbs/blob/a7178b12b041f5b304f4076aa01efed817ba8040/s…) Parseable checking code in RDoc https://github.com/ruby/rdoc/blob/14a7631a3775e033791f13baa3be76c94b908e3d/… ``` def parseable? text ... eval("BEGIN { throw :valid, true }\n#{text}") ... end ``` However, RBS doesn't seem to use RDoc, so I think it's not a big problem. -- https://bugs.ruby-lang.org/

3 2

[ruby-core:120960] [Ruby master Bug#21130] Update net-imap for ruby 3.2, 3.3, 3.4
by nevans (Nicholas Evans) 14 Feb '25

14 Feb '25

Issue #21130 has been reported by nevans (Nicholas Evans). ---------------------------------------- Bug #21130: Update net-imap for ruby 3.2, 3.3, 3.4 https://bugs.ruby-lang.org/issues/21130 * Author: nevans (Nicholas Evans) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The bundled versions are vulnerable to CVE-2024-25186 (https://www.cve.org/CVERecord?id=CVE-2025-25186) Fixing the issue requires upgrading to v0.3.8, v0.4.19, or v0.5.4. * ruby 3.2.7 bundles net-imap v0.3.4.1 PR: Bump net-imap to 0.3.8 for Ruby 3.2 https://github.com/ruby/ruby/pull/12733 * ruby 3.3.7 bundles net-imap v0.4.9.1 PR: Bump net-imap to 0.4.19 for Ruby 3.3 https://github.com/ruby/ruby/pull/12732 * ruby 3.4.1 bundles net-imap v0.5.4 PR: Bump net-imap to v0.5.6 for Ruby 3.4 https://github.com/ruby/ruby/pull/12731 The workaround is to uninstall the vulnerable bundled versions and `gem install net-imap`. -- https://bugs.ruby-lang.org/

2 1

[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