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

[ruby-core:123831] [Ruby Bug#21692] Basic gems like `date` require a compiler
by getajobmike (Mike Perham) 18 Nov '25

18 Nov '25

Issue #21692 has been reported by getajobmike (Mike Perham). ---------------------------------------- Bug #21692: Basic gems like `date` require a compiler https://bugs.ruby-lang.org/issues/21692 * Author: getajobmike (Mike Perham) * Status: Open * ruby -v: 3.4.5 * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I'm trying to use Ruby in a high security environment which does not allow a compiler to be installed. This was easy years ago when all of standard library was included with Ruby itself and I could use `apt install ruby`. But as the standard library has broken off into separate, optional gems it has become impossible to `bundle` a reasonable pure Ruby application without requiring basic gems like `date` which require a compiler to install. Are there any plans to make native extensions optional for gems? With tools like ZJIT it can be better to use pure Ruby for performance; I would like to see Ruby encourage fewer native extensions and/or make them optional. -- https://bugs.ruby-lang.org/

3 4

[ruby-core:122411] [Ruby Bug#21396] Set#initialize should call Set#add on items passed in
by tenderlovemaking (Aaron Patterson) 18 Nov '25

18 Nov '25

Issue #21396 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Bug #21396: Set#initialize should call Set#add on items passed in https://bugs.ruby-lang.org/issues/21396 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ```ruby class Foo < Set def add(item) = super(item.bytesize) end x = Foo.new(["foo"]) p x p x.include?(3) ``` On Ruby 3.4 the output is this: ``` > ruby -v test.rb ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [arm64-darwin24] #<Foo: {3}> true ``` On Ruby master the output is this: ``` > make run ./miniruby -I./lib -I. -I.ext/common -r./arm64-darwin24-fake ./test.rb #<Set: {"foo"}> false ``` The bug is that `initialize` is not calling `add` for the elements passed in, so the subclass doesn't get a chance to change them. I've sent a PR here: https://github.com/ruby/ruby/pull/13518 -- https://bugs.ruby-lang.org/

5 13

[ruby-core:123806] [Ruby Bug#21687] IO＃pos goes wrong after EOF character(ctrl-z) met.
by YO4 (Yoshinao Muramatsu) 17 Nov '25

17 Nov '25

Issue #21687 has been reported by YO4 (Yoshinao Muramatsu). ---------------------------------------- Bug #21687: IO＃pos goes wrong after EOF character(ctrl-z) met. https://bugs.ruby-lang.org/issues/21687 * Author: YO4 (Yoshinao Muramatsu) * Status: Open * ruby -v: ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [x64-mingw-ucrt] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- In Windows environment, when opening a file with the "r", encountering an EOF character (Ctrl-Z, "\x1A") during reading causes the IO to report END-OF-FILE. ```ruby require 'tempfile' Tempfile.open do |f| str = "0123456789\x1A" f.write(str + "x"*(1024_0 - str.bytesize)) f.rewind p f.readline.size # => 10 p f.pos # => 8191, shuld be 10 but equals rbuf size end ``` When the file reaches its end, the file position moves to the position after the last character. Therefore, when encountering the EOF character, the file position is expected to move to the position of the EOF character. This is somewhat unrelated, but I understand that self.seek(0, File::SEEK_END) not positioning at the EOF character is a known limitation. -- https://bugs.ruby-lang.org/

1 2

[ruby-core:119998] [Ruby master Bug#20907] Fiber scheduler does not correctly re-lock mutex if `Mutex#sleep` is interrupted.
by ioquatix (Samuel Williams) 17 Nov '25

17 Nov '25

Issue #20907 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #20907: Fiber scheduler does not correctly re-lock mutex if `Mutex#sleep` is interrupted. https://bugs.ruby-lang.org/issues/20907 * Author: ioquatix (Samuel Williams) * Status: Open * Assignee: ioquatix (Samuel Williams) * Backport: 3.1: REQUIRED, 3.2: REQUIRED, 3.3: REQUIRED ---------------------------------------- The following test fails with a `ThreadError` instead of a `RuntimeError`: ```ruby def test_condition_variable condition_variable = ::Thread::ConditionVariable.new mutex = ::Thread::Mutex.new error = nil thread = Thread.new do Thread.current.report_on_exception = false scheduler = Scheduler.new Fiber.set_scheduler scheduler fiber = Fiber.schedule do begin mutex.synchronize do condition_variable.wait(mutex) end rescue => error end end fiber.raise(RuntimeError) end thread.join assert_kind_of RuntimeError, error end ``` Fix: https://github.com/ruby/ruby/pull/12158 -- https://bugs.ruby-lang.org/

3 3

[ruby-core:123804] [Ruby Bug#21686] In combination with IO#ungetbyte, the write position may become unpredictable.
by YO4 (Yoshinao Muramatsu) 16 Nov '25

16 Nov '25

Issue #21686 has been reported by YO4 (Yoshinao Muramatsu). ---------------------------------------- Bug #21686: In combination with IO#ungetbyte, the write position may become unpredictable. https://bugs.ruby-lang.org/issues/21686 * Author: YO4 (Yoshinao Muramatsu) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x64-mingw-ucrt] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- In the current implementation, using `IO#ungetbyte` can cause `IO#pos` to become negative. Writing to the same file descriptor in this state will result in unexpected write positions. ```ruby require 'tempfile' Tempfile.open do |f| f.write("0123456789") f.rewind f.getbyte # rbuf filled f.ungetbyte("-") # f.pos => 0 f.ungetbyte("-") # f.pos => -1 f.write("x") # seek to -1 failed in io_unread f.rewind p f.read # => "0123456789x", wrote at the end, questionable end ``` When internal `io_unread()` in `io.c` is called to prepare for a write operation while the actual file position is advancing due to reading, lseek fails because it attempts to reset to a negative file position. `IO#seek` has a similar issue. ```ruby Tempfile.open do |f| f.write("0123456789") f.rewind f.getbyte # rbuf filled f.ungetbyte("-") # f.pos => 0 f.ungetbyte("-") # f.pos => -1 f.seek(0, File::SEEK_CUR) p f.pos # => 10, this points to the last of rbuf. end ``` I am preparing the PR, but I understand that there is discussion about the position where the write occurs and the possibility of the pos becoming negative. -- https://bugs.ruby-lang.org/

2 3

[ruby-core:123626] [Ruby Bug#21659] rstring.h error: missing initializer for field ‘len’ of ‘struct RString’ [-Werror=missing-field-initializers] starting in ruby-3.3.10
by wsfulton (William Fulton) 14 Nov '25

14 Nov '25

Issue #21659 has been reported by wsfulton (William Fulton). ---------------------------------------- Bug #21659: rstring.h error: missing initializer for field ‘len’ of ‘struct RString’ [-Werror=missing-field-initializers] starting in ruby-3.3.10 https://bugs.ruby-lang.org/issues/21659 * Author: wsfulton (William Fulton) * Status: Open * ruby -v: ruby 3.3.10 (2025-10-23 revision 343ea05002) [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- All extensions now have this error when using -Werror -Wmissing-field-initializers: ``` In file included from /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby/internal/arithmetic/char.h:29, from /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby/internal/arithmetic.h:24, from /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby/ruby.h:28, from /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby.h:38, from example_wrap.c:1008: /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby/internal/core/rstring.h: In function ‘rbimpl_rstring_getmem’: /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby/internal/core/rstring.h:398:16: error: missing initializer for field ‘len’ of ‘struct RString’ [-Werror=missing-field-initializers] 398 | struct RString retval = {RBASIC_INIT}; | ^~~~~~~ /home/runner/.rvm/rubies/ruby-3.3.10/include/ruby-3.3.0/ruby/internal/core/rstring.h:206:10: note: ‘len’ declared here 206 | long len; | ^~~ ``` Can you please test with warnings turned on as this now breaks all extensions that rely on Ruby.h being warning free. Looks like it is due to commit https://github.com/ruby/ruby/commit/5a8d7642168f4ea0d9331fded3033c225bbc36c5 and expect that ```c++ struct RString retval = {RBASIC_INIT}; ``` should have been changed to: ```c++ struct RString retval = {RBASIC_INIT, 0}; ``` in rstring.h as well as all in the actual Ruby code base. -- https://bugs.ruby-lang.org/

6 12

[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