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

[ruby-core:122515] [Ruby Bug#21436] Date#ajd returns incorrect positive values due to integer overflow for large negative years
by Stranger6667 (Dmitry Dygalo) 11 Jun '25

11 Jun '25

Issue #21436 has been reported by Stranger6667 (Dmitry Dygalo). ---------------------------------------- Bug #21436: Date#ajd returns incorrect positive values due to integer overflow for large negative years https://bugs.ruby-lang.org/issues/21436 * Author: Stranger6667 (Dmitry Dygalo) * Status: Open * ruby -v: 3.2.8 - 3.4.4 (and older versions too) * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- `Date#ajd` (astronomical Julian Day number) returns incorrect positive values instead of negative values for certain large negative years due to signed integer overflow in the `RB_INT2FIX` function. ```ruby require 'date' # Works correctly Date.civil(-110823815392979, 2, 19).ajd #=> (-80956797141128945/2) # BUG - returns positive instead of negative Date.civil(-11082381539297990, 2, 19).ajd #=> (1127692322401036327/2) # Should be negative! # Works correctly (takes a different code path) Date.civil(-111111111082381539297990, 2, 19).ajd #=> (-81166666645679714453739481/2) ``` In [ext/date/date_core.c](https://github.com/ruby/ruby/blob/v3_4_4/ext/date/dat…, the `ir` value can overflow ```c if (FIXNUM_P(r) && FIX2LONG(r) <= (FIXNUM_MAX / 2)) { long ir = FIX2LONG(r); ir = ir * 2 - 1; // On Date.civil(-11082381539297990, 2, 19).ajd // // ir = -8095679714453739481 return rb_rational_new2(LONG2FIX(ir), INT2FIX(2)); // Overflow in LONG2FIX } ``` Then in [include/ruby/internal/arithmetic/long.h](https://github.com/ruby/ruby/blob/… (`LONG2FIX` is an alias for `RB_INT2FIX`) ```c static inline VALUE RB_INT2FIX(long i) { RBIMPL_ASSERT_OR_ASSUME(RB_FIXABLE(i)); /* :NOTE: VALUE can be wider than long. As j being unsigned, 2j+1 is fully * defined. Also it can be compiled into a single LEA instruction. */ const unsigned long j = RBIMPL_CAST((unsigned long)i); const unsigned long k = (j << 1) + RUBY_FIXNUM_FLAG; const long l = RBIMPL_CAST((long)k); const SIGNED_VALUE m = l; /* Sign extend */ const VALUE n = RBIMPL_CAST((VALUE)m); RBIMPL_ASSERT_OR_ASSUME(RB_FIXNUM_P(n)); return n; } ``` It effectively goes: ``` j = (unsigned long)-8095679714453739481 // 10351064359255812135 k = (10351064359255812135 << 1) + RUBY_FIXNUM_FLAG // 2255384644802072655 ... ``` So, `2255384644802072655` encodes `1127692322401036327`, which is the numerator for the observed `ajd` return value in the reproducer above. It also affects `Date` comparisons (since `ajd` is used in `cmp_gen`) -- https://bugs.ruby-lang.org/

1 0

[ruby-core:122261] [Ruby Bug#21368] Moving objects with finalizer between Ractors crashes
by peterzhu2118 (Peter Zhu) 11 Jun '25

11 Jun '25

Issue #21368 has been reported by peterzhu2118 (Peter Zhu). ---------------------------------------- Bug #21368: Moving objects with finalizer between Ractors crashes https://bugs.ruby-lang.org/issues/21368 * Author: peterzhu2118 (Peter Zhu) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- When an object is moved to a different Ractor, the finalizers are not copied to the new object, so it will have the `FL_FINALIZE` flag set but no entry in the finalizer table. The following script crashes: ```ruby r = Ractor.new do loop { Ractor.receive } end 1_000.times do o = Object.new ObjectSpace.define_finalizer(o, proc { |id| }) r.send(o, move: true) end ``` -- https://bugs.ruby-lang.org/

3 5

[ruby-core:118577] [Ruby master Bug#20631] Build failure with Xcode 16 beta and macOS 15 (Sequoia) Beta
by hsbt (Hiroshi SHIBATA) 10 Jun '25

10 Jun '25

Issue #20631 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #20631: Build failure with Xcode 16 beta and macOS 15 (Sequoia) Beta https://bugs.ruby-lang.org/issues/20631 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I found some issues with Xcode 16 beta and macOS 15 (Sequoia) Beta. `TestRubyOptions` and `TestVMDump` are failed with them. full log: https://gist.github.com/hsbt/378fe2ba47e734f2562ba9a154e1795b I'm not sure why macOS require `sudo` command for that. ---- And I and @katei also found the regression of https://bugs.ruby-lang.org/issues/18912#note-15. ``` >> pid = fork { p File.realpath "/" } >> Process.waitpid(pid) objc[82573]: +[NSPlaceholderMutableString initialize] may have been in progress in another thread when fork() was called. objc[82573]: +[NSPlaceholderMutableString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug. => 82573 ``` -- https://bugs.ruby-lang.org/

2 8

[ruby-core:122352] [Ruby Bug#21388] make install and bundled gems
by MSP-Greg (Greg L) 10 Jun '25

10 Jun '25

Issue #21388 has been reported by MSP-Greg (Greg L). ---------------------------------------- Bug #21388: make install and bundled gems https://bugs.ruby-lang.org/issues/21388 * Author: MSP-Greg (Greg L) * Status: Open * ruby -v: ruby 3.5.0dev (2025-05-31T09:43:52Z master 32c708efbd) +PRISM [x64-mingw-ucrt] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Two issues: 1. Currently, `make install` from the `MinGW (UCRT)` workflow shows two gems not being installed (`syslog` cannot be installed on Windows): ``` skipped bundled gems: csv-3.3.5.gem not found in bundled_gems power_assert-2.0.6dev.gem not found in bundled_gems syslog-0.3.0.gem not found in bundled_gems ``` A simple patch file will fix this: ```patch diff --git a/gems/bundled_gems b/gems/bundled_gems index 8891f1c462..ca66b48ed6 100644 --- a/gems/bundled_gems +++ b/gems/bundled_gems @@ -7,7 +7,7 @@ # if `revision` is not given, "v"+`version` or `version` will be used. minitest 5.25.5 https://github.com/minitest/minitest -power_assert 2.0.5 https://github.com/ruby/power_assert a7dab941153b233d3412e249d25da52a6c5691de +power_assert 2.0.6dev https://github.com/ruby/power_assert a7dab941153b233d3412e249d25da52a6c5691de rake 13.3.0 https://github.com/ruby/rake test-unit 3.6.8 https://github.com/test-unit/test-unit rexml 3.4.1 https://github.com/ruby/rexml @@ -33,7 +33,7 @@ rinda 0.2.0 https://github.com/ruby/rinda drb 2.2.3 https://github.com/ruby/drb nkf 0.2.0 https://github.com/ruby/nkf syslog 0.3.0 https://github.com/ruby/syslog -csv 3.3.4 https://github.com/ruby/csv 69d9886238a504bfac60fa516cd08ad2a855a2a8 +csv 3.3.5 https://github.com/ruby/csv 69d9886238a504bfac60fa516cd08ad2a855a2a8 repl_type_completor 0.1.11 https://github.com/ruby/repl_type_completor 25108aa8d69ddaba0b5da3feff1c0035371524b2 ostruct 0.6.1 https://github.com/ruby/ostruct 50d51248bec5560a102a1024aff4174b31dca8cc pstore 0.2.0 https://github.com/ruby/pstore ``` 2. Sometime ago, one could cache the *.gem files, and they would not be downloaded. Now, regardless of the cache, they are always downloaded. -- https://bugs.ruby-lang.org/

3 3

[ruby-core:118412] [Ruby master Misc#20600] @ruby-lang.org has been migrated to Cloudflare
by shugo (Shugo Maeda) 10 Jun '25

10 Jun '25

Issue #20600 has been reported by shugo (Shugo Maeda). ---------------------------------------- Misc #20600: @ruby-lang.org has been migrated to Cloudflare https://bugs.ruby-lang.org/issues/20600 * Author: shugo (Shugo Maeda) * Status: Open ---------------------------------------- @ruby-lang.org has been migrated to Cloudflare, because ruby-lang.org was migrated from Google Domains to Squarespace, and Squarespace's e-mail forwarding doesn't work with custom MX records including subdomains:( I and Shibata-san are adding e-mail routing rules on Cloudflare, so if you have an e-mail address on ruby-lang.org, please verify the e-mail routing address when receiving an email from Cloudflare. -- https://bugs.ruby-lang.org/

6 13

[ruby-core:122502] [Ruby Feature#14915] Deprecate String#crypt
by jhawthorn (John Hawthorn) 09 Jun '25

09 Jun '25

Issue #14915 has been updated by jhawthorn (John Hawthorn). > even if that removal doesn't happen until Ruby 4. 👀 It's been 6 years, is it worth considering `String#crypt`'s removal again? I'd be happy to update Jeremy's patch and gem (which the docs have recommended using since Ruby 2.6). We ran into it today as @luke-gru found a deadlock when it was used with Ractors (PR is open to fix). I also noticed it does not release the GVL despite being possible for it to take a long time to run (minutes!) with certain arguments. I think it would be best for Ruby not to provide such a badly behaved method. ---------------------------------------- Feature #14915: Deprecate String#crypt https://bugs.ruby-lang.org/issues/14915#change-113694 * Author: jeremyevans0 (Jeremy Evans) * Status: Rejected ---------------------------------------- This method is system and implementation dependent, and the portable usage mentioned in the documentation is not truly portable (doesn't work on OpenBSD) and insecure as it uses DES. For systems that lack a crypt(3) implementation, Ruby will happily substitute a version that only supports DES. It's 2018, using DES should be avoided if at all possible. The only internal usage of String#crypt in Ruby is in Webrick, where it uses DES for basic authentication with an htpasswd file. That could and should be changed to use a more secure hash by default (bcrypt since that's the most secure htpasswd format), or at least allow the user to customize Webrick's authentication. I expect there are few if any users actively using Webrick's htpasswd support. This moves the String#crypt implementation to the string/crypt extension, but leaves the String#crypt core method. The core method prints a deprecation warning, then loads the string/crypt extension. The string/crypt extension undefines the String#crypt core method, then defines the previous implementation. Because extensions use extconf.rb instead of configure for their configuration, this ports the related configure.ac code to extconf.rb. I'm not sure that is done correctly and works on all platforms, it will need testing. For systems that lack a crypt(3) implementation, this modifies the fallback code to only define crypt_r, since that is the only function that String#crypt will call in that case. While the patch just deprecates String#crypt, I think we should plan to remove support from ruby: 2.6: core method deprecated 2.7: core method removed, string/crypt extension ships with ruby 2.8: string/crypt extension moves to external gem, not shipped ---Files-------------------------------- 0001-Deprecate-String-crypt-move-implementation-to-string.patch (20.5 KB) 0001-Deprecate-String-crypt.patch (7.48 KB) 0001-Deprecate-String-crypt.patch (7.35 KB) 0001-Deprecate-String-crypt.patch (7.43 KB) deprecate-string-crypt.patch (6.7 KB) -- https://bugs.ruby-lang.org/

1 0

[ruby-core:122496] [Ruby Bug#21401] ObjectSpace can't count Fibers after using a Ractor
by rmosolgo (Robert Mosolgo) 09 Jun '25

09 Jun '25

Issue #21401 has been reported by rmosolgo (Robert Mosolgo). ---------------------------------------- Bug #21401: ObjectSpace can't count Fibers after using a Ractor https://bugs.ruby-lang.org/issues/21401 * Author: rmosolgo (Robert Mosolgo) * Status: Open * ruby -v: ruby 3.5.0dev (2025-06-09T14:38:29Z master f9966b9b76) +PRISM [x86_64-darwin22] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Hi, thanks for all your great work, Ruby crew! I have a test in my project that uses `ObjectSpace.each_object(Fiber).count` to see how many Fibers have been started by my code. This test started failing when I added other tests using `Ractor`s. I was able to isolate it with this script: ```ruby require "objspace" f = Fiber.new { 1 + 1 } GC.start p ObjectSpace.each_object(Fiber).count # => 2 Ractor.new { 1 + 1 }.take p ObjectSpace.each_object(Fiber).count # => 0 (should be 2) # The fiber _is_ there! p f # #<Fiber:0x0000000100c568a8 ractor_fibers.rb:4 (created)> ``` It seems like `ObjectSpace` can't count fibers for some reason, but I expect it to return the number of Fibers in memory. Other classes like `Hash` and `String` are not affected. It fails on Ruby 3.4.1 and 3.5-dev. I used: - `ruby 3.5.0dev (2025-06-09T14:38:29Z master f9966b9b76) +PRISM [x86_64-darwin22]` - `ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-darwin22]` Please let me know if I can help with anything else in tracking down this bug. Thanks again! -- https://bugs.ruby-lang.org/

2 1

[ruby-core:119683] [Ruby master Feature#20861] Add an environment variable for tuning the default thread quantum
by tenderlovemaking (Aaron Patterson) 08 Jun '25

08 Jun '25

Issue #20861 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Feature #20861: Add an environment variable for tuning the default thread quantum https://bugs.ruby-lang.org/issues/20861 * Author: tenderlovemaking (Aaron Patterson) * Status: Open ---------------------------------------- The default thread quantum is currently [hard coded at 100ms](https://github.com/ruby/ruby/blob/c7708d22c33040a74ea7ac683bf7407d37…. This can impact multithreaded systems that are trying to process Ruby level CPU bound work at the same time as IO work. I would like to add an environment variable `RUBY_THREAD_DEFAULT_QUANTUM_MS` that allows users to specify the default thread quantum (in milliseconds) via an environment variable. It defaults to our current default of 100ms. I've submitted the patch [here](https://github.com/ruby/ruby/pull/11981). Here is a Ruby program to demonstrate the problem: ```ruby def measure x = Process.clock_gettime(Process::CLOCK_MONOTONIC) yield Process.clock_gettime(Process::CLOCK_MONOTONIC) - x end def fib(n) if n < 2 n else fib(n-2) + fib(n-1) end end # find fib that takes ~500ms fib_i = 50.times.find { |i| measure { fib(i) } >= 0.05 } sleep_i = measure { fib(fib_i) } threads = [ Thread.new { 100.times { sleep(sleep_i) # sometimes stalled waiting for fib's quantum to finish } puts "done 1" }, Thread.new { 100.times { fib(fib_i) }; puts "done 2" }, ] # We expect the total time to be about 100 * sleep_i (~5 seconds) because # theoretically the sleep thread could be done nearly completely in parallel to # the fib thread. # # But because the `sleep` thread is iterating over the sleep call, it must wait # for the `fib` thread to complete its quantum, before it can start the next iteration. # # This means each sleep iteration could take up to `sleep_i + 100ms` # # We're calling that stalled time "waste" total = measure { threads.each(&:join) } waste = total - (sleep_i * 100) p TOTAL: total, WASTE: waste ``` The program has two threads. One thread is using CPU time by computing `fib` in a loop. The other thread is simulating IO time by calling `sleep` in a loop. When the `sleep` call completes, it can stall, waiting for the quantum in the fib thread to expire. That means that each iteration on sleep can actually take `sleep time + thread quantum`, or in this case ~600ms when we expected it to only take ~500ms. Ideally, the above program would take `500ms * 100` since all `sleep` calls should be able to execute in parallel with the `fib` calls. Of course this isn't true because the sleep thread must acquire the GVL before it can continue the next iteration, so there will always be _some_ overhead. This feature is for allowing people to tune that overhead. If we run this program with the default quantum the output looks like this: ``` $ ./miniruby -v fibtest.rb ruby 3.4.0dev (2024-11-01T14:49:50Z quantum-computing c7708d22c3) +PRISM [arm64-darwin24] done 2 done 1 {TOTAL: 12.672821999993175, WASTE: 4.960721996147186} ``` The output shows that our program spent about 5 seconds stalled, waiting to acquire the GVL. With this patch we can lower the default quantum, and the output is like this: ``` $ RUBY_THREAD_DEFAULT_QUANTUM_MS=10 ./miniruby -v fibtest.rb ruby 3.4.0dev (2024-11-01T22:06:35Z quantum-computing 087500643d) +PRISM [arm64-darwin24] done 2 done 1 {TOTAL: 8.898526000091806, WASTE: 1.4168260043952614} ``` Specifying the ENV to change the quantum to 10ms lowered our waste in the program to ~1.4 seconds. It's common for web applications to do mixed CPU and IO bound tasks in threads (see the Puma webserver), so it would be great if there was a way to customize the thread quantum depending on your application's workload. -- https://bugs.ruby-lang.org/

11 23

[ruby-core:115981] [Ruby master Bug#20105] Introduce `IO::Stream` or something similar.
by ioquatix (Samuel Williams) 07 Jun '25

07 Jun '25

Issue #20105 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #20105: Introduce `IO::Stream` or something similar. https://bugs.ruby-lang.org/issues/20105 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal * Assignee: ioquatix (Samuel Williams) * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Ruby's IO class has a general model for streaming IO, including some hidden classes like `IO::generic_readable` and `IO::generic_writable`. As Ruby's core IO classes evolve, gems like `openssl` (see `OpenSSL::Buffering`) need to be updated to support changes to the interface. As it stands, there are changes in `IO` which are not copied to `OpenSSL::Buffering`. I'd like to propose we introduce some shared interface for streams that is used by `IO`, `Socket`, and `OpenSSL` to start with. The general interface would be similar to `IO` and allow code like `OpenSSL` to avoid re-implementing the `IO` interface. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:121551] [Ruby Feature#21219] `Object#inspect` accept a list of instance variables to display
by byroot (Jean Boussier) 07 Jun '25

07 Jun '25

Issue #21219 has been reported by byroot (Jean Boussier). ---------------------------------------- Feature #21219: `Object#inspect` accept a list of instance variables to display https://bugs.ruby-lang.org/issues/21219 * Author: byroot (Jean Boussier) * Status: Open ---------------------------------------- ## Context The default `Object#inspect` implementation is quite useful to have a generic representation of objects in error message and similar places. However sometimes objects are referencing other objects with a very large `inspect` representation, making error message hard to understand. In some other cases, some instance variables are holding secrets such as password or private keys, and the default inspect behavior can cause these secrets to be leaked in logs among other places. You can of course define your own `inspect` implementation for any object, but it's not as simple as it may seems because you need to handle circular references, otherwise you can end up with a `SystemStackError`. Also, it's more minor, but since Ruby 2.7, you can no longer access an object's address, so you can't implement an `inspect` method that is consistent with `Object#inspect` From my experience, user defined implementations of `#inspect` are very rare, and I think the above is in part responsible. ## Feature I think it would be useful if the default `Object#inspect` implementation accepted a list of instance variables to display, so that you could very easily hide internal state, either because it's too verbose, or because it is secret: ```ruby require 'logger' logger = Logger.new(STDOUT) class DatabaseConfig def initialize(host, user, password) @host = host @user = user @password = password end def inspect = super(instance_variables: [:@host, :@user]) end env = {db_config: DatabaseConfig.new("localhost", "root", "hunter2")} logger.info("something happened, env: #{env}") ``` ``` INFO -- : something happened, env: {db_config: #<DatabaseConfig:0x00000001002b3a08 @host="localhost", @user="root">} ``` -- https://bugs.ruby-lang.org/

6 9