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

[ruby-core:122596] Cooperation Offer.
by ruby-core＠ruby-lang.org 14 Jul '25

14 Jul '25

Hello!<br> As you can see, this is not a formal email, and unfortunately, it does not mean anything good for you. <br> BUT do not despair, it is not critical. I am going to explain to you everything right now. <br> <br> I have access to your electronic devices, which are the part of the local network you regularly use. <br> I have been tracking your activity for the last few months. <br> <br> How did that happen?<br> You visited some hacked websites with Exploit, and your device was exposed to my malicious software (I bought it in Darknet from specialists in this field).<br> This is a very complex software, operating as Trojan Horse. It updates regularly, and your antivirus can not detect it. <br> The program has a keylogger; it can turn your camera and microphone on and off, send files and provide access to your local network. <br> <br> It took me some time to get access to the information from other devices, and as of now, I have all your contacts with conversations, info about your locations, what you like, your favourite websites, etc. <br> Honestly, I meant nothing bad at first and did that just for fun. This is my hobby. <br> <br> But I got HIV and unfortunately lost my job. <br> And I figured out how to use "my hobby" to get money from you! <br> I recorded a video of you masturbating. This video has a separated screen, where you can be easily recognised; also, it can be clearly seen what sort of video you prefer. <br> Well, I am not proud of this, but I need money to survive. <br> <br> Let's make a deal. You pay me as much as I ask you to, and I won't send this video to your friends, family, and other acquaintances. <br> You should understand, this is not a joke. I can send it by email, through SMS-link, social media, even post it in mass media (I have got some hacked accounts of their admins).<br> So you can become Twitter or Instagram "Star"! <br> <br> To avoid this, you should send me 1,290 USD in Bitcoins on my BTC wallet:124mgnHaGQDnrgTBQ6aAJvehdepafvsVFg<br> <br> If you don't know how to use Bitcoins, search it in Bing or Google <<how can I purchase Bitcoins>> or other stuff like that. <br> I will delete the video as soon as I receive the money. I will also delete the malicious software from your device, and you will never hear from me again. <br> I'll give you 2 days, that's more than enough, I think. Time tracking will start as soon as you open this email, I am monitoring this! <br> <br> And one last thing:<br> It makes no sense to report about this to the police since I am using TOR, so there is no way to track Bitcoin transactions. <br> Don't respond to me (I generated this letter in your account and put the real address of the man who has no idea about this). In such a way, I make it impossible to track me.<br> <br> If you ever do something stupid or against my expectations, I will immediately share this video. <br> Good luck!<br>

2 1

[ruby-core:122054] [Ruby Bug#21333] heap-use-after-free caused by rehash during update
by cyruscyliu (Qiang Liu) 14 Jul '25

14 Jul '25

Issue #21333 has been reported by cyruscyliu (Qiang Liu). ---------------------------------------- Bug #21333: heap-use-after-free caused by rehash during update https://bugs.ruby-lang.org/issues/21333 * Author: cyruscyliu (Qiang Liu) * Status: Open * ruby -v: ruby 3.5.0dev (2025-05-13T08:35:34Z master a6435befa7) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Hi, we found a heap-use-after-free caused by rehash during update ``` $a = (1..1337).to_h { |k| [k, k] } $a.update($b) { |k, o, n| $a.rehash } ``` ``` $ git log | head -n4 commit a6435befa76c2ae0525147f934bd9cd1914ffb8a Author: Jean Boussier <jean.boussier(a)gmail.com> Date: Mon May 12 11:02:17 2025 +0200 $ ./ruby triaged/hash_update.rb `RubyGems' were not loaded. `error_highlight' was not loaded. `did_you_mean' was not loaded. `syntax_suggest' was not loaded. ================================================================= ==227694==ERROR: AddressSanitizer: heap-use-after-free on address 0x52f00000e410 at pc 0x64f4179fa0d5 bp 0x7ffec17cce10 sp 0x7ffec17cce08 WRITE of size 8 at 0x52f00000e410 thread T0 #0 0x64f4179fa0d4 in rb_st_update /media/test/ruby/build/../st.c:1508:23 #1 0x64f417814018 in rb_hash_stlike_update /media/test/ruby/build/../hash.c:1686:12 #2 0x64f417814018 in tbl_update /media/test/ruby/build/../hash.c:1727:15 #3 0x64f417823d09 in rb_hash_update_block_i /media/test/ruby/build/../hash.c:4162:5 #4 0x64f417810576 in hash_ar_foreach_iter /media/test/ruby/build/../hash.c:1302:18 #5 0x64f417810576 in ar_foreach_check /media/test/ruby/build/../hash.c:944:22 #6 0x64f417810576 in hash_foreach_call /media/test/ruby/build/../hash.c:1435:15 #7 0x64f4177a45c6 in rb_ensure /media/test/ruby/build/../eval.c:1074:18 #8 0x64f417810329 in rb_hash_foreach /media/test/ruby/build/../hash.c:1463:9 #9 0x64f41781b88f in rb_hash_update /media/test/ruby/build/../hash.c:4219:13 #10 0x64f417b409db in vm_call_cfunc_with_frame_ /media/test/ruby/build/../vm_insnhelper.c:3798:11 #11 0x64f417b2904a in vm_call_method_each_type /media/test/ruby/build/../vm_insnhelper.c:4776:16 #12 0x64f417b28b13 in vm_call_method /media/test/ruby/build/../vm_insnhelper.c #13 0x64f417af0539 in vm_sendish /media/test/ruby/build/../vm_insnhelper.c:5995:15 #14 0x64f417af0539 in vm_exec_core /media/test/ruby/build/../insns.def:851:11 #15 0x64f417ae5cd7 in rb_vm_exec /media/test/ruby/build/../vm.c #16 0x64f4177a1bf0 in rb_ec_exec_node /media/test/ruby/build/../eval.c:281:9 #17 0x64f4177a1bf0 in ruby_run_node /media/test/ruby/build/../eval.c:319:30 #18 0x64f41779d2b0 in rb_main /media/test/ruby/build/../main.c:42:12 #19 0x64f41779d2b0 in main /media/test/ruby/build/../main.c:62:12 #20 0x72d96ba2a1c9 in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 #21 0x72d96ba2a28a in __libc_start_main csu/../csu/libc-start.c:360:3 #22 0x64f4176c3d94 in _start (/media/test/ruby/build/ruby+0x14bd94) (BuildId: 5c3c6444d00499cf0254892dbef6454db4a9698a) 0x52f00000e410 is located 16 bytes inside of 49152-byte region [0x52f00000e400,0x52f00001a400) freed by thread T0 here: #0 0x64f41775e94a in free (/media/test/ruby/build/ruby+0x1e694a) (BuildId: 5c3c6444d00499cf0254892dbef6454db4a9698a) #1 0x64f4177c944b in rb_gc_impl_free /media/test/ruby/build/../gc/default/default.c:8099:9 #2 0x64f4177c944b in ruby_sized_xfree /media/test/ruby/build/../gc.c:5225:13 #3 0x64f4177c944b in ruby_xfree /media/test/ruby/build/../gc.c:5236:5 #4 0x64f417811e09 in hash_st_free /media/test/ruby/build/../hash.c:1218:5 #5 0x64f417811e09 in rb_hash_rehash /media/test/ruby/build/../hash.c:2026:9 #6 0x64f417b409db in vm_call_cfunc_with_frame_ /media/test/ruby/build/../vm_insnhelper.c:3798:11 #7 0x64f417b2904a in vm_call_method_each_type /media/test/ruby/build/../vm_insnhelper.c:4776:16 #8 0x64f417b28b13 in vm_call_method /media/test/ruby/build/../vm_insnhelper.c #9 0x64f417aed6f3 in vm_sendish /media/test/ruby/build/../vm_insnhelper.c:5995:15 #10 0x64f417aed6f3 in vm_exec_core /media/test/ruby/build/../insns.def:899:11 #11 0x64f417ae5cd7 in rb_vm_exec /media/test/ruby/build/../vm.c #12 0x64f417b5bdcc in invoke_iseq_block_from_c /media/test/ruby/build/../vm.c:1653:12 #13 0x64f417b5bdcc in invoke_block_from_c_bh /media/test/ruby/build/../vm.c:1667:20 #14 0x64f417b0e2a7 in vm_yield_with_cref /media/test/ruby/build/../vm.c:1704:12 #15 0x64f417b0e2a7 in vm_yield /media/test/ruby/build/../vm.c:1712:12 #16 0x64f417b0e2a7 in rb_yield_0 /media/test/ruby/build/../vm_eval.c:1361:12 #17 0x64f417b0e2a7 in rb_yield_values /media/test/ruby/build/../vm_eval.c:1400:16 #18 0x64f417823db5 in rb_hash_update_block_callback /media/test/ruby/build/../hash.c:4148:31 #19 0x64f417823d48 in rb_hash_update_block_callback_insert /media/test/ruby/build/../hash.c:4157:1 #20 0x64f4178225c7 in tbl_update_modify /media/test/ruby/build/../hash.c:1696:15 #21 0x64f4179f9bea in rb_st_update /media/test/ruby/build/../st.c:1498:14 #22 0x64f417814018 in rb_hash_stlike_update /media/test/ruby/build/../hash.c:1686:12 #23 0x64f417814018 in tbl_update /media/test/ruby/build/../hash.c:1727:15 #24 0x64f417823d09 in rb_hash_update_block_i /media/test/ruby/build/../hash.c:4162:5 #25 0x64f417810576 in hash_ar_foreach_iter /media/test/ruby/build/../hash.c:1302:18 #26 0x64f417810576 in ar_foreach_check /media/test/ruby/build/../hash.c:944:22 #27 0x64f417810576 in hash_foreach_call /media/test/ruby/build/../hash.c:1435:15 #28 0x64f4177a45c6 in rb_ensure /media/test/ruby/build/../eval.c:1074:18 #29 0x64f417810329 in rb_hash_foreach /media/test/ruby/build/../hash.c:1463:9 #30 0x64f41781b88f in rb_hash_update /media/test/ruby/build/../hash.c:4219:13 #31 0x64f417b409db in vm_call_cfunc_with_frame_ /media/test/ruby/build/../vm_insnhelper.c:3798:11 #32 0x64f417b2904a in vm_call_method_each_type /media/test/ruby/build/../vm_insnhelper.c:4776:16 #33 0x64f417b28b13 in vm_call_method /media/test/ruby/build/../vm_insnhelper.c #34 0x64f417af0539 in vm_sendish /media/test/ruby/build/../vm_insnhelper.c:5995:15 #35 0x64f417af0539 in vm_exec_core /media/test/ruby/build/../insns.def:851:11 #36 0x64f417ae5cd7 in rb_vm_exec /media/test/ruby/build/../vm.c #37 0x64f4177a1bf0 in rb_ec_exec_node /media/test/ruby/build/../eval.c:281:9 #38 0x64f4177a1bf0 in ruby_run_node /media/test/ruby/build/../eval.c:319:30 #39 0x64f41779d2b0 in rb_main /media/test/ruby/build/../main.c:42:12 #40 0x64f41779d2b0 in main /media/test/ruby/build/../main.c:62:12 #41 0x72d96ba2a1c9 in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 #42 0x72d96ba2a28a in __libc_start_main csu/../csu/libc-start.c:360:3 #43 0x64f4176c3d94 in _start (/media/test/ruby/build/ruby+0x14bd94) (BuildId: 5c3c6444d00499cf0254892dbef6454db4a9698a) previously allocated by thread T0 here: #0 0x64f41775ebe3 in malloc (/media/test/ruby/build/ruby+0x1e6be3) (BuildId: 5c3c6444d00499cf0254892dbef6454db4a9698a) #1 0x64f417805df5 in rb_gc_impl_malloc /media/test/ruby/build/../gc/default/default.c:8114:5 #2 0x64f4177d49f2 in ruby_xmalloc_body /media/test/ruby/build/../gc.c:5116:12 #3 0x64f4177d49f2 in ruby_xmalloc /media/test/ruby/build/../gc.c:5106:34 #4 0x64f4179f44a1 in rb_st_init_existing_table_with_size /media/test/ruby/build/../st.c:559:39 #5 0x64f4179f65b0 in rb_st_init_table_with_size /media/test/ruby/build/../st.c:585:5 #6 0x64f4179f65b0 in rebuild_table /media/test/ruby/build/../st.c:753:19 #7 0x64f4179f65b0 in rebuild_table_if_necessary /media/test/ruby/build/../st.c:1125:9 #8 0x64f4179f6f6b in st_add_direct_with_hash /media/test/ruby/build/../st.c:1187:5 #9 0x64f4179f9cf3 in rb_st_update /media/test/ruby/build/../st.c:1502:13 #10 0x64f417814018 in rb_hash_stlike_update /media/test/ruby/build/../hash.c:1686:12 #11 0x64f417814018 in tbl_update /media/test/ruby/build/../hash.c:1727:15 #12 0x64f417813e82 in rb_hash_aset /media/test/ruby/build/../hash.c #13 0x64f417814510 in rb_hash_set_pair /media/test/ruby/build/../hash.c:3715:5 #14 0x64f417ae1bf3 in vm_yield_with_cfunc /media/test/ruby/build/../vm_insnhelper.c:5161:11 #15 0x64f417b5b7f9 in invoke_block_from_c_bh /media/test/ruby/build/../vm.c:1672:16 #16 0x64f417b0dcca in vm_yield_with_cref /media/test/ruby/build/../vm.c:1704:12 #17 0x64f417b0dcca in vm_yield /media/test/ruby/build/../vm.c:1712:12 #18 0x64f417b0dcca in rb_yield_0 /media/test/ruby/build/../vm_eval.c:1361:12 #19 0x64f417b0dcca in rb_yield /media/test/ruby/build/../vm_eval.c #20 0x64f4179371c7 in range_each_fixnum_loop /media/test/ruby/build/../range.c:1059:9 #21 0x64f4179371c7 in range_each /media/test/ruby/build/../range.c:1096:16 #22 0x64f417b53fd5 in vm_call0_cfunc_with_frame /media/test/ruby/build/../vm_eval.c:164:15 #23 0x64f417b53fd5 in vm_call0_cfunc /media/test/ruby/build/../vm_eval.c:178:12 #24 0x64f417b53fd5 in vm_call0_body /media/test/ruby/build/../vm_eval.c:229:15 #25 0x64f417b57a0a in vm_call0_cc /media/test/ruby/build/../vm_eval.c:101:12 #26 0x64f417b57a0a in rb_call0 /media/test/ruby/build/../vm_eval.c:571:12 #27 0x64f417b0f5f5 in rb_call /media/test/ruby/build/../vm_eval.c:890:12 #28 0x64f417b0f5f5 in iterate_method /media/test/ruby/build/../vm_eval.c:1545:12 #29 0x64f417b0fbf5 in rb_iterate0 /media/test/ruby/build/../vm_eval.c:1487:18 #30 0x64f417b0f287 in rb_iterate_internal /media/test/ruby/build/../vm_eval.c:1519:12 #31 0x64f417b0f287 in rb_block_call_kw /media/test/ruby/build/../vm_eval.c:1568:12 #32 0x64f417b0f287 in rb_block_call /media/test/ruby/build/../vm_eval.c:1554:12 #33 0x64f417dad5e0 in enum_hashify_into /media/test/ruby/build/../enum.c:743:5 #34 0x64f417dad5e0 in enum_hashify /media/test/ruby/build/../enum.c:750:12 #35 0x64f417dad5e0 in enum_to_h /media/test/ruby/build/../enum.c:791:12 #36 0x64f417b409db in vm_call_cfunc_with_frame_ /media/test/ruby/build/../vm_insnhelper.c:3798:11 #37 0x64f417b2904a in vm_call_method_each_type /media/test/ruby/build/../vm_insnhelper.c:4776:16 #38 0x64f417b28b13 in vm_call_method /media/test/ruby/build/../vm_insnhelper.c #39 0x64f417af0539 in vm_sendish /media/test/ruby/build/../vm_insnhelper.c:5995:15 #40 0x64f417af0539 in vm_exec_core /media/test/ruby/build/../insns.def:851:11 #41 0x64f417ae5cd7 in rb_vm_exec /media/test/ruby/build/../vm.c #42 0x64f4177a1bf0 in rb_ec_exec_node /media/test/ruby/build/../eval.c:281:9 #43 0x64f4177a1bf0 in ruby_run_node /media/test/ruby/build/../eval.c:319:30 #44 0x64f41779d2b0 in rb_main /media/test/ruby/build/../main.c:42:12 #45 0x64f41779d2b0 in main /media/test/ruby/build/../main.c:62:12 #46 0x72d96ba2a1c9 in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 #47 0x72d96ba2a28a in __libc_start_main csu/../csu/libc-start.c:360:3 #48 0x64f4176c3d94 in _start (/media/test/ruby/build/ruby+0x14bd94) (BuildId: 5c3c6444d00499cf0254892dbef6454db4a9698a) SUMMARY: AddressSanitizer: heap-use-after-free /media/test/ruby/build/../st.c:1508:23 in rb_st_update Shadow bytes around the buggy address: 0x52f00000e180: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x52f00000e200: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x52f00000e280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x52f00000e300: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x52f00000e380: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x52f00000e400: fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd 0x52f00000e480: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x52f00000e500: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x52f00000e580: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x52f00000e600: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x52f00000e680: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb ==227694==ABORTING triaged/hash_update.rb:3: [BUG] ASAN error ruby 3.5.0dev (2025-05-13T08:35:34Z master a6435befa7) +PRISM [x86_64-linux] -- Control frame information ----------------------------------------------- c:0003 p:---- s:0011 e:000010 CFUNC :update c:0002 p:0029 s:0006 e:000005 EVAL triaged/hash_update.rb:3 [FINISH] c:0001 p:0000 s:0003 E:000be0 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- triaged/hash_update.rb:3:in '<main>' triaged/hash_update.rb:3:in 'update' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 1 -- C level backtrace information ------------------------------------------- ./ruby(___interceptor_backtrace) [0x64f4177086aa] /media/test/ruby/build/ruby(rb_print_backtrace+0x14) [0x64f417e7bc97] /media/test/ruby/build/../vm_dump.c:843 /media/test/ruby/build/ruby(rb_vm_bugreport) /media/test/ruby/build/../vm_dump.c:1175 /media/test/ruby/build/ruby(rb_bug_without_die_internal+0x23c) [0x64f417dd016c] /media/test/ruby/build/../error.c:1097 /media/test/ruby/build/ruby(rb_bug_without_die+0x127) [0x64f417dcfe87] /media/test/ruby/build/../error.c:1106 ./ruby(0x64f4177832aa) [0x64f4177832aa] ./ruby(0x64f417763a2f) [0x64f417763a2f] ./ruby(0x64f417766ab5) [0x64f417766ab5] ./ruby(__asan_report_store8) [0x64f417767bdf] /media/test/ruby/build/ruby(rb_st_update+0xcd5) [0x64f4179fa0d5] /media/test/ruby/build/../st.c:1508 /media/test/ruby/build/ruby(tbl_update+0x139) [0x64f417814019] /media/test/ruby/build/../hash.c:1686 /media/test/ruby/build/ruby(rb_hash_update_block_i+0x3a) [0x64f417823d0a] /media/test/ruby/build/../hash.c:4162 /media/test/ruby/build/ruby(hash_ar_foreach_iter+0x10) [0x64f417810577] /media/test/ruby/build/../hash.c:1302 /media/test/ruby/build/ruby(ar_foreach_check) /media/test/ruby/build/../hash.c:944 /media/test/ruby/build/ruby(hash_foreach_call) /media/test/ruby/build/../hash.c:1435 /media/test/ruby/build/ruby(rb_ensure+0x257) [0x64f4177a45c7] /media/test/ruby/build/../eval.c:1074 /media/test/ruby/build/ruby(rb_hash_foreach+0x23a) [0x64f41781032a] /media/test/ruby/build/../hash.c:1463 /media/test/ruby/build/ruby(rb_hash_update+0xe0) [0x64f41781b890] /media/test/ruby/build/../hash.c:4219 /media/test/ruby/build/ruby(vm_cfp_consistent_p+0x0) [0x64f417b409dc] ../vm_insnhelper.c:3798 /media/test/ruby/build/ruby(vm_call_cfunc_with_frame_) ../vm_insnhelper.c:3800 /media/test/ruby/build/ruby(vm_call_method_each_type+0x27b) [0x64f417b2904b] ../vm_insnhelper.c:4776 ./ruby(vm_call_method+0x2d4) [0x64f417b28b14] /media/test/ruby/build/ruby(vm_sendish+0x11f) [0x64f417af053a] ../vm_insnhelper.c:5995 /media/test/ruby/build/ruby(vm_exec_core) ../insns.def:851 ./ruby(vm_exec_loop+0x0) [0x64f417ae5cd8] /media/test/ruby/build/ruby(rb_vm_exec) /media/test/ruby/build/../vm.c:2626 /media/test/ruby/build/ruby(rb_ec_exec_node+0x53) [0x64f4177a1bf1] /media/test/ruby/build/../eval.c:281 /media/test/ruby/build/ruby(ruby_run_node) /media/test/ruby/build/../eval.c:319 /media/test/ruby/build/ruby(rb_main+0x29) [0x64f41779d2b1] /media/test/ruby/build/../main.c:42 /media/test/ruby/build/ruby(main) /media/test/ruby/build/../main.c:62 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_call_main+0x7a) [0x72d96ba2a1ca] ../sysdeps/nptl/libc_start_call_main.h:58 /lib/x86_64-linux-gnu/libc.so.6(call_init+0x0) [0x72d96ba2a28b] ../csu/libc-start.c:360 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main_impl) ../csu/libc-start.c:347 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main) (null):0 ./ruby(_start) [0x64f4176c3d95] -- Other runtime information ----------------------------------------------- * Loaded script: triaged/hash_update.rb * Loaded features: 0 enumerator.so 1 thread.rb 2 fiber.so 3 rational.so 4 complex.so 5 ruby2_keywords.rb 6 set.rb ``` -- https://bugs.ruby-lang.org/

6 8

[ruby-core:121437] [Ruby Bug#21197] Prism does not accept newline after defined? keyword
by kddnewton (Kevin Newton) 14 Jul '25

14 Jul '25

Issue #21197 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Bug #21197: Prism does not accept newline after defined? keyword https://bugs.ruby-lang.org/issues/21197 * Author: kddnewton (Kevin Newton) * Status: Open * Assignee: prism * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ``` defined? (1) ``` -- https://bugs.ruby-lang.org/

2 3

[ruby-core:122154] [Ruby Feature#21346] Introduce `String#ensure_suffix`
by matheusrich (Matheus Richard) 14 Jul '25

14 Jul '25

Issue #21346 has been reported by matheusrich (Matheus Richard). ---------------------------------------- Feature #21346: Introduce `String#ensure_suffix` https://bugs.ruby-lang.org/issues/21346 * Author: matheusrich (Matheus Richard) * Status: Open ---------------------------------------- ## Problem Ensuring a string has a specific suffix or prefix is a common operation in many applications. Bundler itself uses it: https://github.com/rubygems/rubygems/blob/d409ec8b5fc647fabe30e37e17cd1ea85… Here are [GitHub search](https://github.com/search) queries that might find this pattern in other places: 1. for Ruby: `/end(?:s)?_with\?$['"].*['"]$ \?/ lang:ruby -is:fork` 1. for Crystal (a language very similar to Ruby): `/ends_with\?$['"].*['"]$ \?/ lang:crystal -is:fork` ## Suggested solution I believe Ruby would benefit from having a first-class method for this purpose. I suggest the `String#ensure_suffix` and `String#ensure_prefix` methods. I think these names are intuitive enough (here are 2 examples of people using `ensure` for this purpose ([1](https://github.com/boltops-tools/ufo/blob/796104fdb89163d09a58fad42add69…, [2](https://github.com/mumuki/mumuki-domain/blob/6194089d82b1a0c8805ecba98e0…)) I've gone ahead and implemented `String#ensure_suffix` in a [pull request](https://github.com/ruby/ruby/pull/13366) but the suggested behavior is this: ```rb "Hell".ensure_suffix("o!") # => "Hello!" "Hello!".ensure_suffix("o!") # => "Hello!" s = "Hello!" s.ensure_suffix("!").equal?(s) # => true # returns same object if already suffixed ``` -- https://bugs.ruby-lang.org/

8 20

[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:122731] [Ruby Bug#21510] Rails server crashes on Mac M2 with Bus Error at 0x0000000109946aac
by jkvithanage (Janaka Vithanage) 12 Jul '25

12 Jul '25

Issue #21510 has been reported by jkvithanage (Janaka Vithanage). ---------------------------------------- Bug #21510: Rails server crashes on Mac M2 with Bus Error at 0x0000000109946aac https://bugs.ruby-lang.org/issues/21510 * Author: jkvithanage (Janaka Vithanage) * Status: Open * ruby -v: ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-darwin24] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I have been struggling to setup a Rails 5.1.7 application on my Macbook M2 for months. I installed Rosetta, x86_64 brew and my terminal app is set to run with Rosetta. ``` shell ~ ❯ arch i386 ~ ❯ which brew /usr/local/bin/brew ~ ❯ brew list ==> Formulae abseil coreutils icu4c@77 lz4 pkgconf xz autoconf gdbm krb5 m4 postgresql@14 yarn automake gettext libffi mysql protobuf@29 zlib bison gh libnghttp2 node readline zstd brotli git libtool node-build redis c-ares glib libunistring nodenv ruby-install ca-certificates gmp libuv openssl@3 shared-mime-info chruby heroku libyaml pcre2 terminal-notifier ==> Casks ~ ❯ ``` `bundle install` works perfectly fine. Then I can run rails commands like `rails console` and `rails db:` commands with no issues. I can also execute commands inside `rails console` too. `rails server` launches the server as well, but as soon as I accessed the port 3000 on the browser, it crashes with this bus error. ``` Started GET "/" for ::1 at 2025-07-12 22:54:20 +1000 /Users/jkv-mbp/.gem/ruby/2.6.6/gems/pg-0.21.0/lib/pg.rb:56: [BUG] Bus Error at 0x0000000109946aac ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-darwin24] -- Crash Report log information -------------------------------------------- See Crash Report log file under the one of following: * ~/Library/Logs/DiagnosticReports * /Library/Logs/DiagnosticReports for more details. Don't forget to include the above Crash Report log file in bug reports. ``` It seems like an issue related to `pg` gem. Since this doesn't work on macOS, I installed Asahi Linux on it and setup the application. Although, its `aarch64` linux, the application can be launched without any issues. But, it's not a reliable solution for my work setup. It would be great someone can help me with this issue. I have attached a complete crash report and the Gemfile of the project. ---Files-------------------------------- server.log (657 KB) Gemfile (5.93 KB) -- https://bugs.ruby-lang.org/

2 2

[ruby-core:122730] [Ruby Bug#18903] Stack overflow signal handling seems to be triggered once and then not working after
by soulcutter (Bradley Schaefer) 11 Jul '25

11 Jul '25

Issue #18903 has been updated by soulcutter (Bradley Schaefer). One observation I have is that there are ways to prevent this in application code: ```ruby require 'json' circular_reference_hash = {}.tap { |h| h[:self] = h } # Globally JSON.dump_default_options[:max_nesting] = 100 JSON.dump(circular_reference_hash) # More-specifically # JSON.dump(obj, io = nil, limit = nil) Dumps obj as a JSON string, i.e. JSON.dump(circular_reference_hash, nil, 100) ``` I picked `100`, because that happens to be the default `max_nesting` option in `JSON.generate` (and also `to_json`, which uses the same defaults). I guess I'm wondering why `dump` has unsafe defaults in comparison to `generate` - maybe dump's defaults could match generate's (at least for `max_nesting`)? ---------------------------------------- Bug #18903: Stack overflow signal handling seems to be triggered once and then not working after https://bugs.ruby-lang.org/issues/18903#change-114011 * Author: chrisseaton (Chris Seaton) * Status: Open * ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- This program creates a recursive object graph and then tries to convert it to JSON with no max depth, so it stack overflows in C code that does no co-operative stack overflow checks, as the bytecode interpreter would. This therefore triggers a segmentation fault and the stack overflow detection there. It works the first time, but the second time around it doesn't and the program hard crashes on M1. Is there something like a guard page permission that is switched during the handling, and needs to switched back for the guard page to work again? Note that it isn't JSON specific - I think any stack overflow within C code would do it. ```ruby require 'json' a = [] a << a begin JSON.dump(a) rescue Exception puts 'rescued' end JSON.dump(a) ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:122729] [Ruby Bug#21509] io/wait: IO#wait raises error when passed nil as timeout
by chucke (Tiago Cardoso) 11 Jul '25

11 Jul '25

Issue #21509 has been reported by chucke (Tiago Cardoso). ---------------------------------------- Bug #21509: io/wait: IO#wait raises error when passed nil as timeout https://bugs.ruby-lang.org/issues/21509 * Author: chucke (Tiago Cardoso) * Status: Open * ruby -v: 3.4.4 * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The [documentation of the method](https://ruby-doc.org/3.4.1/exts/io/wait/IO.html#method-i-wait) goes: wait(timeout = nil, mode = :read) → self, true, or false However, when passing `nil` in the first argument, it fails: io.wait(nil, :read_write) #=> in 'IO#wait': can't convert NilClass into time interval (TypeError) This seems inconsistent with other variants and related methods: io.wait(IO::READABLE | IO::WRITABLE, nil) #=> 5 io.to_io.wait_readable(nil) #=> returns the socket -- https://bugs.ruby-lang.org/

1 0

[ruby-core:122658] [Ruby Feature#21501] Include native filenames in backtraces as sources for native methods
by ivoanjo (Ivo Anjo) 11 Jul '25

11 Jul '25

Issue #21501 has been reported by ivoanjo (Ivo Anjo). ---------------------------------------- Feature #21501: Include native filenames in backtraces as sources for native methods https://bugs.ruby-lang.org/issues/21501 * Author: ivoanjo (Ivo Anjo) * Status: Open ---------------------------------------- Consider this example: ```ruby require 'bigdecimal' BigDecimal.singleton_class.prepend( Module.new do def save_rounding_mode super end end ) [:example].each do BigDecimal.save_rounding_mode do puts caller sleep 1 end end ``` which Ruby will print as (from 3.4, since https://bugs.ruby-lang.org/issues/19117) ``` native-filenames-example.rb:6:in 'BigDecimal.save_rounding_mode' native-filenames-example.rb:6:in 'save_rounding_mode' native-filenames-example.rb:12:in 'block in <main>' native-filenames-example.rb:11:in 'Array#each' native-filenames-example.rb:11:in '<main>' ``` Having the class names helps, but I think this behavior can still be confusing. Without looking at the code, and understanding that `Array#each` and `BigDecimal.save_rounding_mode` are written in native code, it can be confusing to see them be assigned to `native-filenames-example.rb` in the backtrace. I would like to propose that, whenever possible (see notes below), Ruby shows the name of the native filename where a method was defined. This would result on the backtrace becoming: ``` /rvm/gems/ruby-3.4.4/gems/bigdecimal-3.2.2/lib/bigdecimal.so:0:in 'BigDecimal.save_rounding_mode' native-filenames-example.rb:6:in 'save_rounding_mode' native-filenames-example.rb:12:in 'block in <main>' /rvm/rubies/ruby-3.4.4/lib/libruby.so.3.4:0:in 'Array#each' native-filenames-example.rb:11:in '<main>' ``` or, alternatively, this mechanism could be applied only to extensions, not to libruby/the ruby binary (it's not particularly hard to detect and exclude it): ``` /rvm/gems/ruby-3.4.4/gems/bigdecimal-3.2.2/lib/bigdecimal.so:0:in 'BigDecimal.save_rounding_mode' native-filenames-example.rb:6:in 'save_rounding_mode' native-filenames-example.rb:12:in 'block in <main>' native-filenames-example.rb:11:in 'Array#each' # Don't touch array ;) native-filenames-example.rb:11:in '<main>' ``` This would make it even easier to understand what's coming from where, and I believe it's a great complement to showing the class names. Furthermore, displaying the actual native libraries matches really well with the semantics we get for regular Ruby files: if I were to look on my machine, I would see `/rvm/gems/ruby-3.4.4/gems/bigdecimal-3.2.2/lib/bigdecimal.so` and `/rvm/rubies/ruby-3.4.4/lib/libruby.so.3.4`. And if I moved them, or overrode them, and loaded them from a different path, I would see the difference. (I say this because in the past I've thought about displaying the actual source .c files and lines, but that a) requires debug information; and b) the files often no longer exist in the filesystem; c) is much harder to implement cross-os). --- The extra cool thing is that this is really, really easy to implement! I actually created a [micro gem to show this off](https://github.com/ivoanjo/native-filenames/blob/main/ext/native_filen… as [well as added this as a feature to the Datadog Ruby profiler](https://github.com/DataDog/dd-trace-rb/pull/4745). Other than checking for headers and whatnot, fetching the info can be implemented in 41 lines of C: https://github.com/ivoanjo/native-filenames/blob/main/ext/native_filenames_… and works in Linux, macOS and Windows! The way it works is, we can use the function pointer passed to `rb_define_method`, looking it put using `dladdr` (or some of the other variants shown in the code). Then, given just the function pointer, we can get a path back. It's as simple as that -- it can be added transparently as part of storing the cfunc. And if for some reason the path is not available, we could fall back to the current behavior. I'd be very happy to contribute a PR to make this change, but I decided to start with a proposal first as I realize not everyone may be as excited about this idea as I am ;) -- https://bugs.ruby-lang.org/

5 9