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

[ruby-core:120579] [Ruby master Feature#21020] Sync sig directory for prism of default gem.
by ksss (Yuki Kurihara) 18 Jul '25

18 Jul '25

Issue #21020 has been reported by ksss (Yuki Kurihara). ---------------------------------------- Feature #21020: Sync sig directory for prism of default gem. https://bugs.ruby-lang.org/issues/21020 * Author: ksss (Yuki Kurihara) * Status: Open ---------------------------------------- Currently, the type signatures (RBS) for the default gem is not available. **Prism** is the only default gem with type signatures, but this number is expected to increase in the future. As a first step to resolving this issue, I propose including the `sig` directory of Prism as a default gem in the synchronization process. PR: https://github.com/ruby/ruby/pull/12541 -- https://bugs.ruby-lang.org/

5 5

[ruby-core:112664] [Ruby master Bug#19473] can't be called from trap context (ThreadError) is too limiting
by Eregon (Benoit Daloze) 15 Jul '25

15 Jul '25

Issue #19473 has been reported by Eregon (Benoit Daloze). ---------------------------------------- Bug #19473: can't be called from trap context (ThreadError) is too limiting https://bugs.ruby-lang.org/issues/19473 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Simple reproducer: ``` $ ruby -ve 'm=Mutex.new; trap(:HUP) { m.synchronize { p :OK } }; Process.kill :HUP, Process.pid; sleep 0.1' ruby 3.2.1 (2023-02-08 revision 31819e82c8) [x86_64-linux] -e:1:in `synchronize': can't be called from trap context (ThreadError) from -e:1:in `block in <main>' from -e:1:in `kill' from -e:1:in `<main>' ``` Expected behavior: ``` $ ruby -ve 'm=Mutex.new; trap(:HUP) { m.synchronize { p :OK } }; Process.kill :HUP, Process.pid; sleep 0.1' truffleruby 22.3.1, like ruby 3.0.3, GraalVM CE Native [x86_64-linux] :OK $ ruby -ve 'm=Mutex.new; trap(:HUP) { m.synchronize { p :OK } }; Process.kill :HUP, Process.pid; sleep 0.1' jruby 9.4.0.0 (3.1.0) 2022-11-23 95c0ec159f OpenJDK 64-Bit Server VM 17.0.6+10 on 17.0.6+10 +jit [x86_64-linux] :OK ``` This exception is highly problematic, for instance it breaks `Timeout.timeout` in `trap`: https://github.com/ruby/timeout/issues/17#issuecomment-1142035939 I suppose this behavior is because *sometimes* it's problematic to lock a Mutex in trap, e.g., if it's already locked by the main thread/fiber. However, that's just one case, not all, so we should not raise an exception early like that. There seems to be no valid reason to prevent *all* `Mutex#synchronize` in `trap`. After all, if the Mutex for instance is only used in `trap`, it's well-defined AFAIK. For instance a given trap handler does not seem executed concurrently: ``` $ ruby -ve 'trap(:HUP) { puts "in trap\n"+caller.join("\n")+"\n\n"; sleep 0.1 }; pid = Process.pid; Process.wait fork { 20.times { Process.kill :HUP, pid } }; sleep 1' ruby 3.2.1 (2023-02-08 revision 31819e82c8) [x86_64-linux] in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' ``` And if the trap handler using the Mutex is never called while the Mutex is held by the main thread/fiber, there is also no problem. -- https://bugs.ruby-lang.org/

8 27

[ruby-core:120833] [Ruby master Bug#21099] TestGc#test_gc_stress_at_startup assertion failure
by sanjioh (Fabio Sangiovanni) 14 Jul '25

14 Jul '25

Issue #21099 has been reported by sanjioh (Fabio Sangiovanni). ---------------------------------------- Bug #21099: TestGc#test_gc_stress_at_startup assertion failure https://bugs.ruby-lang.org/issues/21099 * Author: sanjioh (Fabio Sangiovanni) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) +PRISM [x86_64-darwin24] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Hi all, I'm running macOS 15.2, and on my machine the test `TestGc#test_gc_stress_at_startup` results in an assertion failure. These are my current configure flags: ``` ../configure \ --prefix="$SOURCEDIR/ruby_3.4.1" \ --enable-debug-env \ --enable-devel \ cppflags="-DRUBY_DEBUG" \ optflags="-O0 -fno-omit-frame-pointer" ``` make command line for running tests (invoked from the build directory): ``` make test-all TESTS="../test/ruby/test_gc.rb --name=TestGc#test_gc_stress_at_startup" ``` output: ``` Run options: --seed=7555 "--ruby=./miniruby -I../lib -I. -I.ext/common ../tool/runruby.rb --extout=.ext -- --disable-gems" --excludes-dir=../test/.excludes --name=!/memory_leak/ --name=TestGc#test_gc_stress_at_startup # Running tests: [1/1] TestGc#test_gc_stress_at_startup = 3.18 s 1) Failure: TestGc#test_gc_stress_at_startup [/Users/fabio/ruby_xcode/ruby/test/ruby/test_gc.rb:776]: [Bug #15784] pid 16632 killed by SIGABRT (signal 6) | ../gc/default/default.c:1714: Assertion Failed: heap_add_poolpage:page->freelist != NULL | ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) [x86_64-darwin24] | | -- Crash Report log information -------------------------------------------- | See Crash Report log file in one of the following locations: | * ~/Library/Logs/DiagnosticReports | * /Library/Logs/DiagnosticReports | for more details. | Don't forget to include the above Crash Report log file in bug reports. | | -- Control frame information ----------------------------------------------- | c:0001 p:---- s:0003 e:000002 DUMMY [FINISH] | | | -- Threading information --------------------------------------------------- | Total ractor count: 0 | Ruby thread count for this ractor: 0 | | -- C level backtrace information ------------------------------------------- | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace+0x1d) [0x10515014d] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:823 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace) (null):0 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_vm_bugreport+0x2c1) [0x105150431] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:1155 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x156) [0x104e41056] /Users/fabio/ruby_xcode/ruby/build/../error.c:1215 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x0) [0x104e40f00] /Users/fabio/ruby_xcode/ruby/build/../error.c:1191 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure) (null):0 | /Users/fabio/ruby_xcode/ruby/build/ruby(heap_add_poolpage+0xa9) [0x104e84ea9] ../gc/default/default.c:1714 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_step+0x204) [0x104e80224] ../gc/default/default.c:3941 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_rest+0x53) [0x104e7fff3] ../gc/default/default.c:3979 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep+0x98) [0x104e7c418] ../gc/default/default.c:4151 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_start+0x5f9) [0x104e86159] ../gc/default/default.c:6472 | /Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect+0x2c) [0x104e87bbc] ../gc/default/default.c:6351 | /Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect_with_gvl+0xb4) [0x104e8dbc4] ../gc/default/default.c:6753 | /Users/fabio/ruby_xcode/ruby/build/ruby(objspace_malloc_gc_stress+0x8f) [0x104e8daff] ../gc/default/default.c:7996 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_gc_impl_malloc+0x49) [0x104e8d8f9] ../gc/default/default.c:8207 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2_body+0x32) [0x104e76a82] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4699 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2+0x1d) [0x104e76a3d] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4693 | /Users/fabio/ruby_xcode/ruby/build/ruby(pin_array_list_new+0x6f) [0x10511ab3f] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4389 | /Users/fabio/ruby_xcode/ruby/build/ruby(Init_vm_objects+0x1b) [0x10511aa6b] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4446 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_setup+0x46) [0x104e4f0e6] /Users/fabio/ruby_xcode/ruby/build/../eval.c:82 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_init+0xd) [0x104e4f3fd] /Users/fabio/ruby_xcode/ruby/build/../eval.c:98 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_main+0x2b) [0x104d2e6bb] /Users/fabio/ruby_xcode/ruby/build/../main.c:39 | /Users/fabio/ruby_xcode/ruby/build/ruby(main+0x62) [0x104d2e662] /Users/fabio/ruby_xcode/ruby/build/../main.c:65 | | -- Other runtime information ----------------------------------------------- | | * Process memory map: | | 104d2d000-105308000 r-x /Users/fabio/ruby_xcode/ruby/build/ruby | 105308000-105315000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby | 105315000-105317000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby | 105317000-10532c000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby | 10532c000-105500000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby | 105500000-105502000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105502000-105507000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105507000-105508000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105508000-10550c000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 10550c000-10550d000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 10550d000-105516000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105516000-105517000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105517000-105518000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105518000-105521000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105521000-105522000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105522000-105523000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105523000-105524000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105524000-10552b000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105530000-105540000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105573000-1055d3000 r-x /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055d3000-1055d7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055d7000-1055db000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055db000-1055e7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055e7000-105c3e000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby | 105c3e000-106295000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby | 600000000000-600020000000 rw- | 7f9643f00000-7f9644000000 rw- | 7f9644000000-7f9644800000 rw- | 7f9644800000-7f9644900000 rw- | 7f9644900000-7f9644901000 rw- | 7f9644a00000-7f9644b00000 rw- | 7ff7b71d3000-7ff7ba9d3000 --- | 7ff7ba9d3000-7ff7bb1d3000 rw- | 7ff800000000-7ff840000000 r-- | 7ff840000000-7ff844b02000 r-- | 7ff844b02000-7ff844b4a000 r-- | 7ff844b4a000-7ff844c00000 rw- | 7ff844c00000-7ff844e00000 rw- | 7ff844e00000-7ff845000000 rw- | 7ff845000000-7ff845200000 rw- | 7ff845200000-7ff845400000 rw- | 7ff845400000-7ff845600000 rw- | 7ff845600000-7ff880000000 r-- | 7ff880000000-7ffd40000000 r-- | 7ffd40000000-7ffd44400000 r-- | 7ffd44400000-7ffd44600000 rw- | 7ffd44600000-7ffd44800000 rw- | 7ffd44800000-7ffd80000000 r-- | 7ffd80000000-7ffffe000000 r-- | 7fffffe00000-7fffffe01000 r-- | 7ffffffad000-7ffffffae000 r-x | [IMPORTANT] | Don't forget to include the Crash Report log file under | DiagnosticReports directory in bug reports. | . 1. [2/3] Assertion for "stderr" | <[]> expected but was | <["../gc/default/default.c:1714: Assertion Failed: heap_add_poolpage:page->freelist != NULL", | "ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) [x86_64-darwin24]", | "", | "-- Crash Report log information --------------------------------------------", | " See Crash Report log file in one of the following locations:", | " * ~/Library/Logs/DiagnosticReports", | " * /Library/Logs/DiagnosticReports", | " for more details.", | "Don't forget to include the above Crash Report log file in bug reports.", | "", | "-- Control frame information -----------------------------------------------", | "c:0001 p:---- s:0003 e:000002 DUMMY [FINISH]", | "", | "", | "-- Threading information ---------------------------------------------------", | "Total ractor count: 0", | "Ruby thread count for this ractor: 0", | "", | "-- C level backtrace information -------------------------------------------", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace+0x1d) [0x10515014d] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:823", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace) (null):0", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_vm_bugreport+0x2c1) [0x105150431] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:1155", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x156) [0x104e41056] /Users/fabio/ruby_xcode/ruby/build/../error.c:1215", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x0) [0x104e40f00] /Users/fabio/ruby_xcode/ruby/build/../error.c:1191", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure) (null):0", | "/Users/fabio/ruby_xcode/ruby/build/ruby(heap_add_poolpage+0xa9) [0x104e84ea9] ../gc/default/default.c:1714", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_step+0x204) [0x104e80224] ../gc/default/default.c:3941", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_rest+0x53) [0x104e7fff3] ../gc/default/default.c:3979", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep+0x98) [0x104e7c418] ../gc/default/default.c:4151", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_start+0x5f9) [0x104e86159] ../gc/default/default.c:6472", | "/Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect+0x2c) [0x104e87bbc] ../gc/default/default.c:6351", | "/Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect_with_gvl+0xb4) [0x104e8dbc4] ../gc/default/default.c:6753", | "/Users/fabio/ruby_xcode/ruby/build/ruby(objspace_malloc_gc_stress+0x8f) [0x104e8daff] ../gc/default/default.c:7996", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_gc_impl_malloc+0x49) [0x104e8d8f9] ../gc/default/default.c:8207", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2_body+0x32) [0x104e76a82] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4699", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2+0x1d) [0x104e76a3d] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4693", | "/Users/fabio/ruby_xcode/ruby/build/ruby(pin_array_list_new+0x6f) [0x10511ab3f] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4389", | "/Users/fabio/ruby_xcode/ruby/build/ruby(Init_vm_objects+0x1b) [0x10511aa6b] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4446", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_setup+0x46) [0x104e4f0e6] /Users/fabio/ruby_xcode/ruby/build/../eval.c:82", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_init+0xd) [0x104e4f3fd] /Users/fabio/ruby_xcode/ruby/build/../eval.c:98", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_main+0x2b) [0x104d2e6bb] /Users/fabio/ruby_xcode/ruby/build/../main.c:39", | "/Users/fabio/ruby_xcode/ruby/build/ruby(main+0x62) [0x104d2e662] /Users/fabio/ruby_xcode/ruby/build/../main.c:65", | "", | "-- Other runtime information -----------------------------------------------", | "", | "* Process memory map:", | "", | "104d2d000-105308000 r-x /Users/fabio/ruby_xcode/ruby/build/ruby", | "105308000-105315000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby", | "105315000-105317000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby", | "105317000-10532c000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby", | "10532c000-105500000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby", | "105500000-105502000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105502000-105507000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105507000-105508000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105508000-10550c000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "10550c000-10550d000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "10550d000-105516000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105516000-105517000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105517000-105518000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105518000-105521000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105521000-105522000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105522000-105523000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105523000-105524000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105524000-10552b000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105530000-105540000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105573000-1055d3000 r-x /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055d3000-1055d7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055d7000-1055db000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055db000-1055e7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055e7000-105c3e000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby", | "105c3e000-106295000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby", | "600000000000-600020000000 rw-", | "7f9643f00000-7f9644000000 rw-", | "7f9644000000-7f9644800000 rw-", | "7f9644800000-7f9644900000 rw-", | "7f9644900000-7f9644901000 rw-", | "7f9644a00000-7f9644b00000 rw-", | "7ff7b71d3000-7ff7ba9d3000 ---", | "7ff7ba9d3000-7ff7bb1d3000 rw-", | "7ff800000000-7ff840000000 r--", | "7ff840000000-7ff844b02000 r--", | "7ff844b02000-7ff844b4a000 r--", | "7ff844b4a000-7ff844c00000 rw-", | "7ff844c00000-7ff844e00000 rw-", | "7ff844e00000-7ff845000000 rw-", | "7ff845000000-7ff845200000 rw-", | "7ff845200000-7ff845400000 rw-", | "7ff845400000-7ff845600000 rw-", | "7ff845600000-7ff880000000 r--", | "7ff880000000-7ffd40000000 r--", | "7ffd40000000-7ffd44400000 r--", | "7ffd44400000-7ffd44600000 rw-", | "7ffd44600000-7ffd44800000 rw-", | "7ffd44800000-7ffd80000000 r--", | "7ffd80000000-7ffffe000000 r--", | "7fffffe00000-7fffffe01000 r--", | "7ffffffad000-7ffffffae000 r-x", | "[IMPORTANT]", | "Don't forget to include the Crash Report log file under", | "DiagnosticReports directory in bug reports.", | ""]>. 2. [3/3] Assertion for "success?" | Expected #<Process::Status: pid 16632 SIGABRT (signal 6)> to be success?. Finished tests in 3.208725s, 0.3117 tests/s, 1.8699 assertions/s. 1 tests, 6 assertions, 1 failures, 0 errors, 0 skips ruby -v: ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) +PRISM [x86_64-darwin24] make: *** [uncommon.mk:965: yes-test-all] Error 1 ``` -- https://bugs.ruby-lang.org/

3 3

[ruby-core:120618] [Ruby master Bug#21029] Prism behavior for `defined? (;x)` differs
by qnighy (Masaki Hara) 14 Jul '25

14 Jul '25

Issue #21029 has been reported by qnighy (Masaki Hara). ---------------------------------------- Bug #21029: Prism behavior for `defined? (;x)` differs https://bugs.ruby-lang.org/issues/21029 * Author: qnighy (Masaki Hara) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-11T03:21:57Z master 1b3037081e) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Prism has a different behavior for `(;expr)` when used in `defined?` predicate: ```console % ./miniruby --parser=prism -e "p defined? (;x)" nil % ./miniruby --parser=parse.y -e "p defined? (;x)" "expression" ``` Although not a significant difference, aligning either of them with the other would be better. -- https://bugs.ruby-lang.org/

5 11

[ruby-core:111027] [Ruby master Bug#19154] Specify require and autoload guarantees in ractors
by fxn (Xavier Noria) 14 Jul '25

14 Jul '25

Issue #19154 has been reported by fxn (Xavier Noria). ---------------------------------------- Bug #19154: Specify require and autoload guarantees in ractors https://bugs.ruby-lang.org/issues/19154 * Author: fxn (Xavier Noria) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0preview3 (2022-11-27) [x86_64-darwin22] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Given a file `c.rb`: ```ruby class C end ``` the following script: ```ruby r1 = Ractor.new do require './c.rb' end r2 = Ractor.new do require './c.rb' end r1.take r2.take ``` raises: ``` % ruby -v foo.rb ruby 3.2.0preview3 (2022-11-27) [x86_64-darwin22] foo.rb:1: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues. #<Thread:0x000000010fee2928 run> terminated with exception (report_on_exception is true): #<Thread:0x00000001102acfe0 run> terminated with exception (report_on_exception is true): <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:164:in `ensure in require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:167:in `require' from foo.rb:6:in `block in <main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:37:in `require'<internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:164:in `ensure in require': : can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:167:in `require' can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from foo.rb:2:in `block in <main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:37:in `require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from foo.rb:2:in `block in <main>' from foo.rb:6:in `block in <main>' <internal:ractor>:698:in `take': thrown by remote Ractor. (Ractor::RemoteError) from foo.rb:9:in `<main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:164:in `ensure in require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:167:in `require' from foo.rb:2:in `block in <main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:37:in `require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from foo.rb:2:in `block in <main>' ``` Would it be possible to have documentation about their interaction? This is important also to understand autoloading within ractors, since constant references may trigger `require` calls. -- https://bugs.ruby-lang.org/

5 13

[ruby-core:117392] [Ruby master Feature#20405] Inline comments
by nobu (Nobuyoshi Nakada) 08 Jul '25

08 Jul '25

Issue #20405 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Feature #20405: Inline comments https://bugs.ruby-lang.org/issues/20405 * Author: nobu (Nobuyoshi Nakada) * Status: Open ---------------------------------------- I propose a new inline comment syntax. ```ruby p (| This is a comment (| and nested one |) /:|) (:|) #=> :| ``` -- https://bugs.ruby-lang.org/

7 10

[ruby-core:115203] [Ruby master Bug#19981] bootstraptest/test_ractor.rb: Segmentation fault on arm32
by jaruga (Jun Aruga) 02 Jul '25

02 Jul '25

Issue #19981 has been reported by jaruga (Jun Aruga). ---------------------------------------- Bug #19981: bootstraptest/test_ractor.rb: Segmentation fault on arm32 https://bugs.ruby-lang.org/issues/19981 * Author: jaruga (Jun Aruga) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I faced the following segmentation fault on Ubuntu jammy arm32 (emulated environment by `SETARCH='setarch linux32 --verbose --32bit'`) in both Travis CI arm64 [log](https://app.travis-ci.com/github/ruby/ruby/jobs/612418476#L2422 ) and RubyCI arm64-neoverse server. I tested it on the latest ruby master branch `14fa5e39d72c84d3e12e10dc5d77a6e6200c10f5`. I was able to reproduce this issue on RubyCI arm64-neoverse server, and prepared the reproducing script. So, you can try to debug on the server. It seems that the `-O3` flag triggered the issue. Because I didn't see the issue when Travis CI setting `- optflags=-O1` in `.travis.yml` on the current master branch. https://github.com/junaruga/report-ruby-ractor-segmentation-fault ``` + arm-linux-gnueabihf-gcc --version arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 + setarch linux32 --verbose --32bit make -s test Switching on ADDR_LIMIT_32BIT. Execute command `make'. Fstderr output is not empty <internal:ractor>:760: [BUG] Segmentation fault at 0x0000000c ruby 3.3.0dev (2023-10-30T09:27:06Z master 14fa5e39d7) [armv8l-linux-eabihf] -- Control frame information ----------------------------------------------- c:0005 p:0003 s:0021 e:000020 METHOD <internal:ractor>:760 c:0004 p:0008 s:0014 e:000013 BLOCK bootstraptest.test_ractor.rb_541_1260.rb:4 c:0003 p:0018 s:0011 e:000010 METHOD <internal:kernel>:187 c:0002 p:0004 s:0006 e:000005 BLOCK bootstraptest.test_ractor.rb_541_1260.rb:3 [FINISH] c:0001 p:---- s:0003 e:000002 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- bootstraptest.test_ractor.rb_541_1260.rb:3:in `block in <main>' <internal:kernel>:187:in `loop' bootstraptest.test_ractor.rb_541_1260.rb:4:in `block (2 levels) in <main>' <internal:ractor>:760:in `yield' -- Threading information --------------------------------------------------- Total ractor count: 2 Ruby thread count for this ractor: 1 -- Machine register context ------------------------------------------------ r0: 0x00000000 r1: 0x00000001 r2: 0x00000007 r3: 0x00000000 r4: 0x00c935c8 r5: 0x00000002 r6: 0x00000002 r7: 0x00000000 r8: 0x00000004 r9: 0x00c646b0 r10: 0x00000002 sp: 0xd5d91c90 fau: 0x0000000c -- Other runtime information ----------------------------------------------- * Loaded script: bootstraptest.test_ractor.rb_541_1260.rb * Loaded features: 0 enumerator.so 1 thread.rb 2 fiber.so 3 rational.so 4 complex.so 5 ruby2_keywords.rb 6 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/encdb.so 7 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/trans/transdb.so * Process memory map: 00640000-0093a000 r-xp 00000000 103:03 29263803 /home/jaruga/git/ruby/ruby/build/ruby 0094a000-0094e000 r--p 002fa000 103:03 29263803 /home/jaruga/git/ruby/ruby/build/ruby 0094e000-0094f000 rw-p 002fe000 103:03 29263803 /home/jaruga/git/ruby/ruby/build/ruby 0094f000-00956000 rw-p 00000000 00:00 0 00bf3000-00cba000 rw-p 00000000 00:00 0 [heap] d5700000-d5721000 rw-p 00000000 00:00 0 d5721000-d5800000 ---p 00000000 00:00 0 d5900000-d5921000 rw-p 00000000 00:00 0 d5921000-d5a00000 ---p 00000000 00:00 0 d5a00000-d5a21000 rw-p 00000000 00:00 0 d5a21000-d5b00000 ---p 00000000 00:00 0 d5b00000-d5b21000 rw-p 00000000 00:00 0 d5b21000-d5c00000 ---p 00000000 00:00 0 d5c5f000-d5c60000 ---p 00000000 00:00 0 d5c60000-d5c90000 rw-p 00000000 00:00 0 d5c9f000-d5ca0000 ---p 00000000 00:00 0 d5ca0000-d5cd0000 rw-p 00000000 00:00 0 d5cde000-d5cdf000 ---p 00000000 00:00 0 d5cdf000-d5cef000 rw-p 00000000 00:00 0 d5cef000-d5cf0000 ---p 00000000 00:00 0 d5cf0000-d5d81000 rw-p 00000000 00:00 0 d5d81000-d5d82000 ---p 00000000 00:00 0 d5d82000-d5e12000 rw-p 00000000 00:00 0 d5e12000-d5e13000 ---p 00000000 00:00 0 d5e13000-d5ea3000 rw-p 00000000 00:00 0 d5ea3000-d5ea4000 ---p 00000000 00:00 0 d5ea4000-d5f34000 rw-p 00000000 00:00 0 d5f34000-d5f35000 ---p 00000000 00:00 0 d5f35000-d5fc5000 rw-p 00000000 00:00 0 d5fc5000-d5fc6000 ---p 00000000 00:00 0 d5fc6000-d6056000 rw-p 00000000 00:00 0 d6056000-d6057000 ---p 00000000 00:00 0 d6057000-d60e7000 rw-p 00000000 00:00 0 d60e7000-d60e8000 ---p 00000000 00:00 0 d60e8000-d6178000 rw-p 00000000 00:00 0 d6178000-d6179000 ---p 00000000 00:00 0 d6179000-d6209000 rw-p 00000000 00:00 0 d6209000-d620a000 ---p 00000000 00:00 0 d620a000-d629a000 rw-p 00000000 00:00 0 d629a000-d629b000 ---p 00000000 00:00 0 d629b000-d632b000 rw-p 00000000 00:00 0 d632b000-d632c000 ---p 00000000 00:00 0 d632c000-f5d10000 rw-p 00000000 00:00 0 f5d10000-f5d12000 r-xp 00000000 103:03 29263555 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/trans/transdb.so f5d12000-f5d21000 ---p 00002000 103:03 29263555 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/trans/transdb.so f5d21000-f5d22000 r--p 00001000 103:03 29263555 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/trans/transdb.so f5d22000-f5d23000 rw-p 00002000 103:03 29263555 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/trans/transdb.so f5d30000-f5d32000 r-xp 00000000 103:03 29263548 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/encdb.so f5d32000-f5d41000 ---p 00002000 103:03 29263548 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/encdb.so f5d41000-f5d42000 r--p 00001000 103:03 29263548 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/encdb.so f5d42000-f5d43000 rw-p 00002000 103:03 29263548 /home/jaruga/git/ruby/ruby/build/.ext/armv8l-linux-eabihf/enc/encdb.so f5d4f000-f5d50000 ---p 00000000 00:00 0 f5d50000-f5d71000 rw-p 00000000 00:00 0 f5d71000-f5d72000 ---p 00000000 00:00 0 f5d72000-f5d93000 rw-p 00000000 00:00 0 f5d93000-f5d94000 ---p 00000000 00:00 0 f5d94000-f5db5000 rw-p 00000000 00:00 0 f5db5000-f5db6000 ---p 00000000 00:00 0 f5db6000-f5dd7000 rw-p 00000000 00:00 0 f5dd7000-f5dd8000 ---p 00000000 00:00 0 f5dd8000-f5df9000 rw-p 00000000 00:00 0 f5df9000-f5dfa000 ---p 00000000 00:00 0 f5dfa000-f5e1b000 rw-p 00000000 00:00 0 f5e1b000-f5e1c000 ---p 00000000 00:00 0 f5e1c000-f5e3d000 rw-p 00000000 00:00 0 f5e3d000-f5e3e000 ---p 00000000 00:00 0 f5e3e000-f5e5f000 rw-p 00000000 00:00 0 f5e5f000-f5e60000 ---p 00000000 00:00 0 f5e60000-f66a0000 rw-p 00000000 00:00 0 f66af000-f73b0000 rw-p 00000000 00:00 0 f73b5000-f7436000 rw-p 00000000 00:00 0 f7436000-f76b0000 r--p 0006f000 103:03 11802136 /usr/lib/locale/locale-archive f76b0000-f78b0000 r--p 00000000 103:03 11802136 /usr/lib/locale/locale-archive f78b0000-f79bc000 r-xp 00000000 103:03 11670018 /usr/lib/arm-linux-gnueabihf/libc.so.6 f79bc000-f79cc000 ---p 0010c000 103:03 11670018 /usr/lib/arm-linux-gnueabihf/libc.so.6 f79cc000-f79ce000 r--p 0010c000 103:03 11670018 /usr/lib/arm-linux-gnueabihf/libc.so.6 f79ce000-f79cf000 rw-p 0010e000 103:03 11670018 /usr/lib/arm-linux-gnueabihf/libc.so.6 f79cf000-f79d9000 rw-p 00000000 00:00 0 f79e0000-f7a21000 r-xp 00000000 103:03 11670021 /usr/lib/arm-linux-gnueabihf/libm.so.6 f7a21000-f7a30000 ---p 00041000 103:03 11670021 /usr/lib/arm-linux-gnueabihf/libm.so.6 f7a30000-f7a31000 r--p 00040000 103:03 11670021 /usr/lib/arm-linux-gnueabihf/libm.so.6 f7a31000-f7a32000 rw-p 00041000 103:03 11670021 /usr/lib/arm-linux-gnueabihf/libm.so.6 f7a40000-f7a6b000 r-xp 00000000 103:03 11670013 /usr/lib/arm-linux-gnueabihf/libcrypt.so.1.1.0 f7a6b000-f7a7b000 ---p 0002b000 103:03 11670013 /usr/lib/arm-linux-gnueabihf/libcrypt.so.1.1.0 f7a7b000-f7a7c000 r--p 0002b000 103:03 11670013 /usr/lib/arm-linux-gnueabihf/libcrypt.so.1.1.0 f7a7c000-f7a7d000 rw-p 0002c000 103:03 11670013 /usr/lib/arm-linux-gnueabihf/libcrypt.so.1.1.0 f7a7d000-f7a85000 rw-p 00000000 00:00 0 f7a88000-f7aa7000 r-xp 00000000 103:03 11670015 /usr/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3 f7aac000-f7ab3000 r--s 00000000 103:03 11670285 /usr/lib/arm-linux-gnueabihf/gconv/gconv-modules.cache f7ab3000-f7ab5000 rw-p 00000000 00:00 0 f7ab5000-f7ab6000 r-xp 00000000 00:00 0 [sigpage] f7ab6000-f7ab8000 r--p 0001e000 103:03 11670015 /usr/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3 f7ab8000-f7ab9000 rw-p 00020000 103:03 11670015 /usr/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3 ff7dd000-fffdc000 rw-p 00000000 00:00 0 [stack] ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors] ``` -- https://bugs.ruby-lang.org/

2 1

[ruby-core:120601] [Ruby master Bug#21024] Ruby including <cstdbool> generates compilation warning with GCC 15, header is deprecated in C++17,
by jprokop (Jarek Prokop) 02 Jul '25

02 Jul '25

Issue #21024 has been reported by jprokop (Jarek Prokop). ---------------------------------------- Bug #21024: Ruby including <cstdbool> generates compilation warning with GCC 15, header is deprecated in C++17, https://bugs.ruby-lang.org/issues/21024 * Author: jprokop (Jarek Prokop) * Status: Open * ruby -v: ruby 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 ---------------------------------------- C++ compiler in GCC 15 now generates a warning when trying to include `<cstdbool>`. This file is being included when compiling with C++ compiler from `include/ruby/internal/stdbool.h`. In C++, true, false and bool are keywords so including headers for boolean definitions should not be necessary. Alternatively, just including <stdbool.h> should be sufficient as that is what the `#include <cstdbool>` results in with GCC. Simplest fix is just deleting the lines that are including the file (see attached patch and comments 2 and 3 from downstream issue linked in the bottom section "Additional info"). Considering the wide array of compilers Ruby aims to support to be compiled with I wanted to make an issue here first to make sure there isn't a supported compiler that wouldn't agree with this approach. Reproduction: Obtain GCC 15, for Fedora Rawhide there is currently a repo of maintainer, I use it in Fedora Rawhide container (podman is replaceable for docker here): ``` host$ podman run -it --rm registry.fedoraproject.org/fedora:rawhide bash container# echo "[gcc_15] name=pre-release GCC 15 Repo baseurl=https://fedorapeople.org/~dmalcolm/gcc/gcc-15-mass-prebuild/$basear… type=rpm-md skip_if_unavailable=True gpgcheck=0 repo_gpgcheck=0 enabled=1 enabled_metadata=1" > /etc/yum.repos.d/gcc_15.repo container# dnf install --assumeyes g++ ruby-devel ``` ^ should install `g++-15.0.0` and `ruby.h` needed for the reproducer. Note: that baseurl is a custom space of a Fedora maintainer. Have a file named for example `main.cpp`: ``` cpp #include <ruby.h> int main(void) { return 0; } ``` Compile with GCC 15 ``` $ g++ main.cpp ``` Current behavior: Compiling throws warning: ``` $ g++ main.cpp In file included from /usr/include/ruby/internal/stdbool.h:30, from /usr/include/ruby/backward/2/bool.h:22, from /usr/include/ruby/defines.h:74, from /usr/include/ruby/ruby.h:25, from /usr/include/ruby.h:38, from reproducer.cpp:1: /usr/include/c++/15/cstdbool:48:6: warning: #warning "<cstdbool> is deprecated in C++17, remove the #include" [-Wcpp] 48 | # warning "<cstdbool> is deprecated in C++17, remove the #include" | ^~~~~~~ ``` Expected: Compilation throws no warnings and compiles the executable: ``` $ g++ reproducer.cpp $ echo $? 0 ``` Additional info: ``` $ g++ --version g++ (GCC) 15.0.0 20241203 (Red Hat 15.0.0-0) Copyright (C) 2024 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` This was met during recompilation of libdnf5 that includes `-Werror` in their compilation flags, See downstream discussion: https://bugzilla.redhat.com/show_bug.cgi?id=2336567 Considering the inclusion of the <cstdbool> throws me up to 5 years ago back ( https://github.com/ruby/ruby/blob/9e6e39c3512f7a962c44dc3729c98a0f8be90341/… ), I assume this warning will be the case with older rubies as well as newest master when using GCC 15. ---Files-------------------------------- 0001-Stop-including-cstdbool-in-include-ruby-internal-std.patch (869 Bytes) -- https://bugs.ruby-lang.org/

5 6

[ruby-core:120315] [Ruby master Bug#20968] `Array#fetch_values` unexpected method name in stack trace
by koic (Koichi ITO) 24 Jun '25

24 Jun '25

Issue #20968 has been reported by koic (Koichi ITO). ---------------------------------------- Bug #20968: `Array#fetch_values` unexpected method name in stack trace https://bugs.ruby-lang.org/issues/20968 * Author: koic (Koichi ITO) * Status: Open * ruby -v: ruby 3.4.0dev (2024-12-19T04:44:56Z master 2783868de2) +PRISM [x86_64-darwin23] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- It seems that the current Ruby implementation is displaying unexpected method name in stack trace. ## Expected Similar to `Hash#fetch_values`, the method name `Array#fetch_values` is expected to be displayed in the stack trace. ```console $ ruby -e '{k: 42}.fetch_values(:unknown)' -e:1:in 'Hash#fetch_values': key not found: :unknown (KeyError) from -e:1:in '<main>' $ ruby -e '[1].fetch_values(42)' -e:1:in 'Array#fetch_values': index 42 outside of array bounds: -1...1 (IndexError) from -e:1:in '<main>' ``` ## Actual The stack trace displays the `Array#fetch` method, which user is not aware of, along with the `<internal.array>` stack trace. ```console $ ruby -e '[1].fetch_values(42)' <internal:array>:211:in 'Array#fetch': index 42 outside of array bounds: -1...1 (IndexError) from <internal:array>:211:in 'block in Array#fetch_values' from <internal:array>:211:in 'Array#map!' from <internal:array>:211:in 'Array#fetch_values' from -e:1:in '<main>' ``` It likely requires an approach such as implementing it in C, as suggested in https://github.com/ruby/ruby/pull/11555. -- https://bugs.ruby-lang.org/

10 21

[ruby-core:119041] [Ruby master Bug#20714] Handle optional dependencies in `bundled_gems.rb`
by Earlopain (A S) 23 Jun '25

23 Jun '25

Issue #20714 has been reported by Earlopain (A S). ---------------------------------------- Bug #20714: Handle optional dependencies in `bundled_gems.rb` https://bugs.ruby-lang.org/issues/20714 * Author: Earlopain (A S) * Status: Open * ruby -v: 3.3.5 * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I've encountered a few places around bundled gems where the library doesn't care if the gem is available, but will still provide some functionallity if it is. The way to accomplish that right now seems to be by setting `$VERBOSE = nil` and resetting it later again to not bother the user with the warning about the gem. However, this has the effect of silencing the warning about other gems as well, that may not be prepared about the bundling. From `ruby/reline` for example: https://github.com/ruby/reline/blob/c90f08f7e308d2f1cdd7cfaf9939fe45ce546fd… Or the `logging` gem: https://github.com/TwP/logging/blob/df41715364f7eb8c65098cd3c3316677ef1f378… I propose to simply delay the warning to the next require. GitHub PR at ... -- https://bugs.ruby-lang.org/

5 30