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

[ruby-core:121688] [Ruby Feature#21275] Update to Unicode 17.0
by duerst 14 Nov '25

14 Nov '25

Issue #21275 has been reported by duerst (Martin Dürst). ---------------------------------------- Feature #21275: Update to Unicode 17.0 https://bugs.ruby-lang.org/issues/21275 * Author: duerst (Martin Dürst) * Status: Open * Assignee: duerst (Martin Dürst) * Target version: 3.5 ---------------------------------------- Unicode 17.0 is currently in alpha. Beta is planned for late May, release for September 2025. We just updated to Unicode 16.0, so we can start testing with alpha/beta. -- https://bugs.ruby-lang.org/

2 1

[ruby-core:123793] [Ruby Bug#15773] Net::HTTP doesn't try next IP address in case of timeout
by adrienjarthon (Adrien Jarthon) 13 Nov '25

13 Nov '25

Issue #15773 has been updated by adrienjarthon (Adrien Jarthon). I was surprised to notice this is still the case in Ruby 3.3. I understand it could be a lot of work and I'm not asking for it to be implemented by other people right away of course. But at least was there any change in the refusal of implementing this behavior? It's implemented by most other software as already pointed out and strongly recommend for years in the RFC. If there is any ongoing work or if the team is now open to the idea I could provide some help. Thanks! ---------------------------------------- Bug #15773: Net::HTTP doesn't try next IP address in case of timeout https://bugs.ruby-lang.org/issues/15773#change-115192 * Author: nicolasnoble (Nicolas Noble) * Status: Rejected * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- This example requires to have a working IPv6 address. Since IPv6 is used in first priority, I am using it to demonstrate the problem, but it exists with plain IPv4, which will be more round-robin-style, so less deterministic to show a reproduction case. I have made two URLs that have both IPv4 and IPv6 addresses: http://ipv6.grumpycoder.net/ and http://bad-ipv6.grumpycoder.net/ - both URLs should work in an IPv6-enabled web browser, as well as curl or wget for instance. The difference is that the bad-ipv6 subdomain doesn't have an IPv6 that will actually connect. Therefore, browsers, curl and wget will fallback to using the IPv4 when the initial IPv6 connection attempt failed: ``` $ wget -T1 http://bad-ipv6.grumpycoder.net -O - # demonstrating using wget because its output is more clear than curl's verbose --2019-04-16 15:56:52-- http://bad-ipv6.grumpycoder.net/ Resolving bad-ipv6.grumpycoder.net (bad-ipv6.grumpycoder.net) 2001:bc8:3690:200::2, 62.210.214.144 Connecting to bad-ipv6.grumpycoder.net (bad-ipv6.grumpycoder.net)|2001:bc8:3690:200::2|:80... failed: Connection timed out. Connecting to bad-ipv6.grumpycoder.net (bad-ipv6.grumpycoder.net)|62.210.214.144|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 45 [text/html] Saving to: ‘STDOUT’ - 0%[ ] 0 --.-KB/s <html><body><h1>It works!</h1></body></html> - 100%[=====================================================================>] 45 --.-KB/s in 0s 2019-04-16 15:56:53 (6.55 MB/s) - written to stdout [45/45] ``` However, in Ruby, using Net::HTTP (or OpenURI), that's not going to be the case: ``` $ ruby bad-ipv6.rb http://ipv6.grumpycoder.net <html><body><h1>It works!</h1></body></html> http://bad-ipv6.grumpycoder.net Net::OpenTimeout: execution expired ``` Contents of my test file: ```ruby require 'open-uri' ['ipv6', 'bad-ipv6'].each do |s| url = 'http://%s.grumpycoder.net' %[s] puts url begin puts open(url).read rescue StandardError => e puts "#{e.class}: #{e.message}" next end end ``` The proper behavior should be to retry the next IP address and exhaust all of the IPs in the DNS resolution results before throwing out an error. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:123792] [Ruby Misc#21684] Does IO#pos clear the buffer?
by YO4 (Yoshinao Muramatsu) 13 Nov '25

13 Nov '25

Issue #21684 has been reported by YO4 (Yoshinao Muramatsu). ---------------------------------------- Misc #21684: Does IO#pos clear the buffer? https://bugs.ruby-lang.org/issues/21684 * Author: YO4 (Yoshinao Muramatsu) * Status: Open ---------------------------------------- I'm working on io.c and I'm confused by the difference between how the code looks and how it behaves. There is a function `io_unread(rb_io_t *fptr, bool discard_rbuf)` and this seems to discard buffer only if discard_rbuf is truthy. But they discards the buffer regardless of discard_rbuf in an ordinary code path. As a result the buffer is discarded when IO#pos is called. Is this intended? I checked #20869 and [DevMeeting-2024-11-07](https://github.com/ruby/dev-meeting-log/blob/master/…, but I couldn't find a conclusion. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:119895] [Ruby master Bug#20889] IO#ungetc and IO#ungetbyte should not cause IO#pos to report an inaccurate position
by javanthropus (Jeremy Bopp) 13 Nov '25

13 Nov '25

Issue #20889 has been reported by javanthropus (Jeremy Bopp). ---------------------------------------- Bug #20889: IO#ungetc and IO#ungetbyte should not cause IO#pos to report an inaccurate position https://bugs.ruby-lang.org/issues/20889 * Author: javanthropus (Jeremy Bopp) * Status: Open * ruby -v: ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- ```ruby require 'tempfile' Tempfile.open(encoding: 'utf-8') do |f| f.write('0123456789') f.rewind f.ungetbyte(93) f.pos # => -1; negative value is surprising! end Tempfile.open(encoding: 'utf-8') do |f| f.write('0123456789') f.rewind f.ungetc('a'.encode('utf-8')) f.pos # => -1; similar to the ungetbyte case end Tempfile.open(encoding: 'utf-8:utf-16le') do |f| f.write('0123456789') f.rewind f.ungetc('a'.encode('utf-16le')) f.pos # => 0; maybe should be -2 to match the previous ungetc case? end ``` It doesn't seem logical that `IO#pos` should ever be affected by `IO#ungetc` or `IO#ungetbyte`. The pushed characters or bytes aren't really in the stream source. The value of `IO#pos` implies that jumping directly to that position via `IO#seek` and reading from there would return the same character or byte that was pushed, but the pushed characters or bytes are lost when the operation to seek in the stream is performed. In the case where `IO#pos` is a negative value, attempting to seek to that position actually raises an exception. In the `IO#ungetc` with character conversion case above, it seems unreasonable to make `IO#pos` report an even less correct position. In that case, the position would need to be adjusted by 2 bytes in reverse due to the internal encoding of the stream, but that is completely inconsistent with the behavior of `IO#pos` when reading from the stream normally where it reports the underlying stream's byte position and not the number of transcoded bytes that have been read: ```ruby require 'tempfile' Tempfile.open(encoding: 'utf-8:utf-16le') do |f| f.write('0123456789') f.rewind f.getc.bytesize # => 2; due to the internal encoding of the stream f.pos # => 1; reports actual bytes read from the stream, not transcoded bytes end ``` Attempting to use `IO#pos` when there are characters or bytes pushed into the read buffer by way of `IO#ungetc` or `IO#ungetbyte` should result in one of the following behaviors: 1. Raise and exception 2. Return the stream's position, clearing the read buffer entirely 3. Return the stream's position, ignoring the pushed characters or bytes, and produce a warning -- https://bugs.ruby-lang.org/

2 1

[ruby-core:122773] [Ruby Feature#21513] Raise on converting endless range to set
by viralpraxis (Iaroslav Kurbatov) 13 Nov '25

13 Nov '25

Issue #21513 has been reported by viralpraxis (Iaroslav Kurbatov). ---------------------------------------- Feature #21513: Raise on converting endless range to set https://bugs.ruby-lang.org/issues/21513 * Author: viralpraxis (Iaroslav Kurbatov) * Status: Open ---------------------------------------- Converting endless range to array raises: ``` shell ruby -e '(1..).to_a' -e:1:in 'Range#to_a': cannot convert endless range to an array (RangeError) from -e:1:in '<main>' ``` but converting to set does not: ``` shell ruby -e '(1..).to_set # hangs' ``` I think it makes to raise in both cases for consistency. Something like this should do the trick: ``` diff diff --git i/prelude.rb w/prelude.rb index f49cada637..11bfa3fc95 100644 --- i/prelude.rb +++ w/prelude.rb @@ -30,6 +30,10 @@ module Enumerable # Makes a set from the enumerable object with given arguments. # Passing arguments to this method is deprecated. def to_set(*args, &block) + if self.class == Range && self.end.nil? + raise RangeError, "cannot convert endless range to a set" + end + klass = if args.empty? Set else diff --git i/test/ruby/test_range.rb w/test/ruby/test_range.rb index f875c0ab40..27b968641b 100644 --- i/test/ruby/test_range.rb +++ w/test/ruby/test_range.rb @@ -1541,4 +1541,11 @@ def test_overlap? assert_not_operator((1...3), :overlap?, (3..4)) assert_not_operator((...3), :overlap?, (3..)) end + + def test_to_set + assert_equal(Set[], (1..-1).to_set) + assert_equal(Set[1, 2, 3], (1..3).to_set) + + assert_raise(RangeError) { (239..).to_set } + end end ``` If this patch is accepted, I'll open a PR. ``` shell ./ruby -v ruby 3.5.0dev (2025-07-14T20:34:32Z master a6d483971a) +PRISM [x86_64-linux] ``` -- https://bugs.ruby-lang.org/

5 7

[ruby-core:123775] [Ruby Misc#21681] Clarification on the Status and Roadmap of Ruby Box for Ruby 4.0
by dmitry.pogrebnoy (Dmitry Pogrebnoy) 13 Nov '25

13 Nov '25

Issue #21681 has been reported by dmitry.pogrebnoy (Dmitry Pogrebnoy). ---------------------------------------- Misc #21681: Clarification on the Status and Roadmap of Ruby Box for Ruby 4.0 https://bugs.ruby-lang.org/issues/21681 * Author: dmitry.pogrebnoy (Dmitry Pogrebnoy) * Status: Open ---------------------------------------- Hello! I’d like to ask about the expected state of Ruby Box in the upcoming Ruby 4.0 release. I came across the roadmap here: https://bugs.ruby-lang.org/versions/105, which mentions the related feature: https://bugs.ruby-lang.org/issues/21311. From the discussion, it seems there are several concerns around the proposal. I also noticed that the name Ruby Box originated from this thread: https://bugs.ruby-lang.org/issues/21385. In that discussion, it was mentioned that Ruby Box is expected to serve as a low-level API. However, I haven’t found any information about a potential high-level API built on top of it. Since I’d like to plan ahead and ensure that development tools can support this new feature and its adoption, could you please clarify: * Given the threads mentioned above, what is the final vision/scope of the Ruby Box feature? I appreciate if you point me towards relevant documentation. * Is Ruby Box expected to be included by default in Ruby 4.0 (as usual planned for late December if I got it right)? * What is the general plan or roadmap for Ruby Box? Are there any intentions to introduce a high-level API or additional related features? Thank you very much for your time and for any insights you can share. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:123781] [Ruby Bug#18878] parse.y: Foo::Bar {} is inconsistently rejected
by yui-knk (Kaneko Yuichiro) 12 Nov '25

12 Nov '25

Issue #18878 has been updated by yui-knk (Kaneko Yuichiro). Pull Request: https://github.com/ruby/ruby/pull/15165 ---------------------------------------- Bug #18878: parse.y: Foo::Bar {} is inconsistently rejected https://bugs.ruby-lang.org/issues/18878#change-115172 * Author: qnighy (Masaki Hara) * Status: Assigned * Assignee: ydah (Yudai Takada) * ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- The following source doesn't parse: ```ruby Foo::Bar {} ``` despite the following: ```ruby bar # local variable or method call Bar # constant bar() # method call Bar() # method call bar {} # method call Bar {} # method call bar() {} # method call Bar() {} # method call Foo::bar # method call Foo::Bar # constant Foo::bar() # method call Foo::Bar() # method call Foo::bar {} # method call # Foo::Bar {} # SyntaxError Foo::bar() {} # method call Foo::Bar() {} # method call ``` Especially considering `Bar {}`, this looks like a missing implementation rather than an intentional behavior. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:123778] [Ruby Bug#21683] IO#each_codepoint do not take care of encoding when IO uses encoding conversion for reading.
by YO4 (Yoshinao Muramatsu) 12 Nov '25

12 Nov '25

Issue #21683 has been reported by YO4 (Yoshinao Muramatsu). ---------------------------------------- Bug #21683: IO#each_codepoint do not take care of encoding when IO uses encoding conversion for reading. https://bugs.ruby-lang.org/issues/21683 * Author: YO4 (Yoshinao Muramatsu) * Status: Open * ruby -v: ruby 3.5.0dev (2025-11-03T10:33:44Z master 0832e954c9) +PRISM [x64-mingw-ucrt] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- without encoding conversion ```irb irb(main):001> open(File::NULL, 'r') { |f| f.ungetc(%Q[\u{3042}\u{3044}\u{3046}]); f.each_codepoint.map { |c| c.to_s(16) } } => ["3042", "3044", "3046"] # => valid ``` with encoding conversion ```irb irb(main):001> open(File::NULL, 'rt') { |f| f.ungetc(%Q[\u{3042}\u{3044}\u{3046}]); f.each_codepoint.map { |c| c.to_s(16) } } => ["e3", "81", "82", "e3", "81", "84", "e3", "81", "86"] # => invalid ``` prior to ruby 3.4 lacks 6cd98c24fe9aeea3829ac3d554a277f053cec0be (Allow IO#each_codepoint to work with unetc even when encoding conversion active) using ungetbyte can similarly reproduce this. ```irb irb(main):001> open(File::NULL, 'rt') { |f| f.ungetbyte(%Q[\u{3042}\u{3044}\u{3046}]); p f.each_codepoint.map { |c| c.to_s(16) } } => ["e3", "81", "82", "e3", "81", "84", "e3", "81", "86"] ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:123724] [Ruby Bug#21672] `IO::Buffer.new` does not check that flags are valid
by trinistr (Alexander Bulancov) 11 Nov '25

11 Nov '25

Issue #21672 has been reported by trinistr (Alexander Bulancov). ---------------------------------------- Bug #21672: `IO::Buffer.new` does not check that flags are valid https://bugs.ruby-lang.org/issues/21672 * Author: trinistr (Alexander Bulancov) * Status: Open * ruby -v: ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- `IO::Buffer.new` has a `flags` argument that allows to override automatic decision between INTERNAL and MAPPED. As far as I understand, these modes are supposed to be exclusive, however in practice there is no check, and the user is free to specify both: ``` IO::Buffer.new(10, IO::Buffer::MAPPED|IO::Buffer::INTERNAL) # => # #<IO::Buffer 0x0000555bfdccf760+10 INTERNAL MAPPED> # 0x00000000 00 00 00 00 00 00 00 00 00 00 .......... ``` From the source code in https://github.com/ruby/ruby/blob/master/io_buffer.c#L204, the real mode seems to be INTERNAL. I imagine that the order of branches can be reversed with changes, suddenly changing behavior. Even worse, if at least one of `INTERNAL` or `MAPPED` is specified, flags are not checked at all, allowing complete nonsense: ``` IO::Buffer.new(10, 0xffffff) # #<IO::Buffer 0x000055672a653190+10 EXTERNAL INTERNAL MAPPED SHARED LOCKED PRIVATE READONLY> ``` `IO::Buffer.map` also exhibits this issue, though I'm unsure if this combination of flags is actually invalid (it at least doesn't get LOCKED): ``` IO::Buffer.map(File.open('README.md', 'r+'), nil, 0, 0xffffff) # #<IO::Buffer 0x00007fd8edb90000+9024 MAPPED FILE PRIVATE READONLY> ``` -- https://bugs.ruby-lang.org/

4 5

[ruby-core:123538] [Ruby Misc#21647] DevMeeting-2025-11-13
by mame (Yusuke Endoh) 11 Nov '25

11 Nov '25

Issue #21647 has been reported by mame (Yusuke Endoh). ---------------------------------------- Misc #21647: DevMeeting-2025-11-13 https://bugs.ruby-lang.org/issues/21647 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2025/11/13 13:00-17:00** (JST) Log: *TBD* - Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker. - Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly. - Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue). - We will write a record of the discussion in the file or to each ticket in English. - All activities are best-effort (keep in mind that most of us are volunteer developers). - The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time. - *DO NOT* discuss then on this ticket, please. # Call for agenda items If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format: ``` * [Ticket ref] Ticket title (your name) * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.) ``` Example: ``` * [Feature #14609] `Kernel#p` without args shows the receiver (ko1) * I feel this feature is very useful and some people say :+1: so let discuss this feature. ``` - It is recommended to add a comment by 2025/11/10. We hold a preparatory meeting to create an agenda a few days before the dev-meeting. - The format is strict. We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). We may ignore a comment that does not follow the format. - Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion. -- https://bugs.ruby-lang.org/

8 7