- ruby-dev - ml.ruby-lang.org

[ruby-dev:52181] [Ruby Bug#21673] Segmentation Fault in IRB when refining `Kernel#puts` using `Module#refine` (Regression since Ruby 3.4)
by yokomaru (Yoko Suzuki) 29 Nov '25

29 Nov '25

Issue #21673 has been reported by yokomaru (Yoko Suzuki). ---------------------------------------- Bug #21673: Segmentation Fault in IRB when refining `Kernel#puts` using `Module#refine` (Regression since Ruby 3.4) https://bugs.ruby-lang.org/issues/21673 * Author: yokomaru (Yoko Suzuki) * Status: Open * ruby -v: ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [arm64-darwin24] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- In the IRB environment running Ruby 3.4 and later, the VM crashes with a Segmentation Fault when a module refining `Kernel#puts` is defined and `puts` is subsequently executed. The crash does not occur when the exact same code is executed as a regular Ruby script. **Environment** Reproduced on multiple environments: ``` macOS 15.5 (Apple Silicon M1, MacBook Pro) - ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [arm64-darwin24] - ruby 3.5.0dev (2025-11-06 master cf4a034d59) +PRISM [arm64-darwin24] - irb 1.15.3 (also reproduced with 1.13.1) - Installed via rbenv ``` ``` Arch Linux (AArch64) - Linux 6.11.6-arch1-1 - ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [x86_64-linux] - irb 1.15.3 - Installed via mise ``` This does not occur on: Ruby 3.3.10 + IRB 1.13.1 **Steps to Reproduce (Reproduction Script)** The crash reproduces with these steps (on Ruby 3.4+): 1. Start irb. ```bash $ irb ``` 2. Define the refinement module for `Kernel#puts`. ```ruby module Foo refine Kernel do def puts end end end # Explicit 'using Foo' is NOT required ``` 3. Execute `puts` at the IRB prompt. ```ruby puts # ← Segmentation Fault occurs here ``` **Expected Result** As observed in Ruby 3.3.10, the IRB session should continue to operate normally. **Actual Result (Execution Log Excerpt)** The full crash logs (for macOS and Arch Linux) and the macOS crash report are provided in the attached files. ``` $ irb irb(main):001* module Foo irb(main):002* refine Kernel do irb(main):003* def puts irb(main):004* end irb(main):005* end irb(main):006> end => #<refinement:Kernel@Foo> irb(main):007> put/Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb/context.rb:636: [BUG] Segmentation fault at 0x0000000000000030 ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [arm64-darwin24] puts -- 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:0049 p:---- s:0274 e:000273 CFUNC :public_method c:0048 p:---- s:0271 e:000270 CFUNC :bind_call c:0047 p:0221 s:0265 e:000264 METHOD /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb/context.rb:636 c:0046 p:0034 s:0251 e:000250 METHOD /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb/context.rb:648 c:0045 p:0010 s:0239 e:000238 BLOCK /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb/input-method.rb:277 c:0044 p:0024 s:0233 e:000232 METHOD /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/reline-0.6.2/lib/reline/line_editor.rb:787 <...snip...> -- Ruby level backtrace information ---------------------------------------- /Users/USER/.rbenv/versions/3.4.7/bin/irb:25:in '<main>' /Users/USER/.rbenv/versions/3.4.7/bin/irb:25:in 'load' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/exe/irb:9:in '<top (required)>' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb.rb:54:in 'start' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb.rb:173:in 'run' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb.rb:173:in 'catch' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb.rb:174:in 'block in run' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb.rb:193:in 'eval_input' /Users/USER/.rbenv/versions/3.4.7/lib/ruby/gems/3.4.0/gems/irb-1.15.3/lib/irb.rb:278:in 'each_top_level_statement' <internal:kernel>:168:in 'loop' <...snip...> -- C level backtrace information ------------------------------------------- /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_bugreport+0xb6c) [0x102ccdaa8] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_bug_for_fatal_signal+0x100) [0x102b07bfc] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(sigsegv+0x84) [0x102c2e2f4] /usr/lib/system/libsystem_platform.dylib(_sigtramp+0x38) [0x19e60c624] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_callable_method_entry_with_refinements+0xd8) [0x102caabb4] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_callable_method_entry_with_refinements+0xd8) [0x102caabb4] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(obj_method+0x160) [0x102bcbf74] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call0_body+0x35c) [0x102cc4b50] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_call_kw+0xc4) [0x102cae300] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call_cfunc_with_frame_+0xf0) [0x102cbf798] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_exec_core+0x46c8) [0x102ca77f0] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_exec+0x1b4) [0x102ca1fa4] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(invoke_block_from_c_bh+0x36c) [0x102cc7614] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_yield+0xa8) [0x102cafa54] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_ary_each+0x40) [0x102a5b7f8] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call_cfunc_with_frame_+0xf0) [0x102cbf798] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_exec_core+0x2620) [0x102ca5748] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_exec+0x1b4) [0x102ca1fa4] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(invoke_block_from_c_bh+0x36c) [0x102cc7614] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_yield+0xa8) [0x102cafa54] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_protect+0xb0) [0x102b13918] /Users/USER/.rbenv/versions/3.4.7/lib/ruby/3.4.0/arm64-darwin24/io/console.bundle(ttymode+0x1e0) [0x102462ab4] /Users/USER/.rbenv/versions/3.4.7/lib/ruby/3.4.0/arm64-darwin24/io/console.bundle(ttymode) (null):0 /Users/USER/.rbenv/versions/3.4.7/lib/ruby/3.4.0/arm64-darwin24/io/console.bundle(console_raw+0x40) [0x102460ca0] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call_cfunc_with_frame_+0xf0) [0x102cbf798] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_exec_core+0x2620) [0x102ca5748] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_exec+0x134) [0x102ca1f24] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(invoke_block_from_c_bh+0x36c) [0x102cc7614] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_yield+0xa8) [0x102cafa54] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_ensure+0xac) [0x102b13a70] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call_cfunc_with_frame_+0xf0) [0x102cbf798] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_exec_core+0x2620) [0x102ca5748] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_exec+0x134) [0x102ca1f24] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(invoke_block_from_c_bh+0x36c) [0x102cc7614] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(catch_i+0x6c) [0x102cc6d50] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_catch_protect+0xbc) [0x102cb1b70] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_f_catch+0x70) [0x102cb2560] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call_cfunc_with_frame_+0xf0) [0x102cbf798] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_exec_core+0x2620) [0x102ca5748] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_exec+0x1b4) [0x102ca1fa4] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(load_iseq_eval+0x224) [0x102b73b50] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_load_internal+0x84) [0x102b70e8c] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_f_load+0x8c) [0x102b72aa0] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_call_cfunc_with_frame_+0xf0) [0x102cbf798] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(vm_exec_core+0x46c8) [0x102ca77f0] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_vm_exec+0x134) [0x102ca1f24] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(rb_ec_exec_node+0x8c) [0x102b12c14] /Users/USER/.rbenv/versions/3.4.7/lib/libruby.3.4.dylib(ruby_run_node+0x40) [0x102b12b3c] /Users/USER/.rbenv/versions/3.4.7/bin/ruby(main+0x68) [0x1022c0618] ``` ---Files-------------------------------- backtrace_ruby-3.4.7_macos.txt (111 KB) backtrace_ruby-3.4.7_archlinux.txt (90.4 KB) macos_crash_report_ruby-3.4.7.ips.txt (31.4 KB) -- https://bugs.ruby-lang.org/

4 5

[ruby-dev:52176] [Ruby Bug#21666] Math.lgamma(-1).should == [infinity_value, 1] fails with Fedora glibc-2.42.9000-8.fc44
by mtasaka (Mamoru TASAKA) 29 Nov '25

29 Nov '25

Issue #21666 has been reported by mtasaka (Mamoru TASAKA). ---------------------------------------- Bug #21666: Math.lgamma(-1).should == [infinity_value, 1] fails with Fedora glibc-2.42.9000-8.fc44 https://bugs.ruby-lang.org/issues/21666 * Author: mtasaka (Mamoru TASAKA) * Status: Open * ruby -v: ruby 3.5.0dev (2025-11-04 master 55257b5038) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- With Fedora glibc-2.42.9000-8.fc44 the following test: https://github.com/ruby/ruby/blob/cdcb490d2bceb4ff8d6fce349047a2b722e6ae87/… fails like ``` 1) Math.lgamma returns [Infinity, 1] when passed -1 FAILED Expected [Infinity, -1] == [Infinity, 1] to be truthy but was false /builddir/build/BUILD/ruby-3.5.0_20251103.2332git4001e81a8e-build/ruby-3.5.0-4001e81a8e/spec/ruby/core/math/lgamma_spec.rb:10:in 'block (3 levels) in <top (required)>' /builddir/build/BUILD/ruby-3.5.0_20251103.2332git4001e81a8e-build/ruby-3.5.0-4001e81a8e/spec/ruby/core/math/lgamma_spec.rb:3:in '<top (required)>' ``` (With the help from glibc developer: https://bugzilla.redhat.com/show_bug.cgi?id=2412227 ) POSIX.1-2024 says (ref: https://pubs.opengroup.org/onlinepubs/9799919799/functions/lgamma.html ) > If $x$ is a non-positive integer, a pole error shall occur and > lgamma(), lgammaf(), and lgammal() shall return +HUGE_VAL, +HUGE_VALF, and +HUGE_VALL, respectively. but also says: > The sign of $ \Gamma(x) $ shall be returned in the external integer signgam. > If $x$ is NaN, -Inf, or a negative integer, the value of signgam is **unspecified**.` So on this line: https://github.com/ruby/ruby/blob/cdcb490d2bceb4ff8d6fce349047a2b722e6ae87/… when `d` is -1 (or negative integer), the value of `sign` is unspeficied. -- https://bugs.ruby-lang.org/

3 5

[ruby-dev:52175] [Ruby Bug#21663] IO#pos will corrupt the file position in specific situation.
by t_nagaya (Tsutomu Nagaya) 02 Nov '25

02 Nov '25

Issue #21663 has been reported by t_nagaya (Tsutomu Nagaya). ---------------------------------------- Bug #21663: IO#pos will corrupt the file position in specific situation. https://bugs.ruby-lang.org/issues/21663 * Author: t_nagaya (Tsutomu Nagaya) * Status: Open * ruby -v: ruby 3.2.3 (2024-01-18 revision 52bb2ac0a6) [x64-mingw-ucrt] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- `IO#pos` and `IO#tell` will corrupt the file position in the following situation. ### Situation: - Running on Windows. (`RUBY_CRLF_ENVIRONMENT` is defined.) - The filesize is over 0x100000000 bytes. - The file is opened in text mode. - There are several `CRLF`s written around 0x100000000. - Some read operations to fill internal buffer (`rbuf`) has been performed. - The real file position (associated with the file descriptor) is somewhat greater than 0x100000000. ### Code to reproduce: ```ruby file = "./test_file" # Prepare a test file f = File.open(file, "wb:binary") f.truncate(0x100000000) f.pos = f.size - 13 f.puts("0123456789\r\n9876543210\r\n" * 10) f.close # Operations to reproduce f = File.open(file, "r:utf-8") f.seek(0x100000000 - 13) puts "%#x" % f.pos p f.gets puts "%#x" % f.pos p f.gets puts "%#x" % f.pos f.close ``` ### Actual result: ``` 0xfffffff3 "0123456789\n" 0x100000012 "789\n" 0x100000017 ``` ### Expected result: ``` 0xfffffff3 "0123456789\n" 0xffffffff "9876543210\n" 0x10000000b ``` ### Notes: Currently, io.c has the following code. In the above situation, `extra_max` may be set to 0 or a small integer value by casting it as the type `long` (assumed 4 bytes). So `newlines` is set lower than the actual count, the file does not seek back correctly. ```c /* * IO unread with taking care of removed '\r' in text mode. */ static void io_unread(rb_io_t *fptr, bool discard_rbuf) { rb_off_t r, pos; ssize_t read_size; long i; long newlines = 0; long extra_max; char *p; char *buf; rb_io_check_closed(fptr); if (fptr->rbuf.len == 0 || fptr->mode & FMODE_DUPLEX) { return; } errno = 0; if (!rb_w32_fd_is_text(fptr->fd)) { r = lseek(fptr->fd, -fptr->rbuf.len, SEEK_CUR); if (r < 0 && errno) { if (errno == ESPIPE) fptr->mode |= FMODE_DUPLEX; if (!discard_rbuf) return; } goto end; } pos = lseek(fptr->fd, 0, SEEK_CUR); if (pos < 0 && errno) { if (errno == ESPIPE) fptr->mode |= FMODE_DUPLEX; if (!discard_rbuf) goto end; } /* add extra offset for removed '\r' in rbuf */ extra_max = (long)(pos - fptr->rbuf.len); p = fptr->rbuf.ptr + fptr->rbuf.off; /* if the end of rbuf is '\r', rbuf doesn't have '\r' within rbuf.len */ if (*(fptr->rbuf.ptr + fptr->rbuf.capa - 1) == '\r') { newlines++; } for (i = 0; i < fptr->rbuf.len; i++) { if (*p == '\n') newlines++; if (extra_max == newlines) break; p++; } buf = ALLOC_N(char, fptr->rbuf.len + newlines); while (newlines >= 0) { r = lseek(fptr->fd, pos - fptr->rbuf.len - newlines, SEEK_SET); if (newlines == 0) break; if (r < 0) { newlines--; continue; } read_size = _read(fptr->fd, buf, fptr->rbuf.len + newlines); if (read_size < 0) { int e = errno; free(buf); rb_syserr_fail_path(e, fptr->pathv); } if (read_size == fptr->rbuf.len) { lseek(fptr->fd, r, SEEK_SET); break; } else { newlines--; } } free(buf); end: fptr->rbuf.off = 0; fptr->rbuf.len = 0; clear_codeconv(fptr); return; } ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52083] I RECORDED YOU!
by ruby-dev＠ruby-lang.org 17 Oct '25

17 Oct '25

Hello there! Unfortunately, there are some bad news for you. Some time ago your device was infected with my private trojan, R.A.T (Remote Administration Tool), if you want to find out more about it simply use Google. My trojan allowed me to access your files, accounts and your camera. Check the sender of this email, I have sent it from your email account. To make sure you read this email, you will receive it multiple times. You truly enjoy checking out porn websites and watching dirty videos, while having a lot of kinky fun. I RECORDED YOU (through your camera) SATISFYING YOURSELF! After that I removed my malware to not leave any traces. If you still doubt my serious intentions, it only takes couple mouse clicks to share the video of you with your friends, relatives, all email contacts, on social networks, the darknet and to publish all your files. All you need is $1800 USD in Bitcoin (BTC) transfer to my account. After the transaction is successful, I will proceed to delete everything. Be sure, I keep my promises. You can easily buy Bitcoin (BTC) here: https://cex.io/buy-bitcoins https://nexo.com/buy-crypto/bitcoin-btc https://bitpay.com/buy-bitcoin/?crypto=BTC https://paybis.com/ https://invity.io/buy-crypto Or simply google other exchanger. After that send the Bitcoin (BTC) directly to my wallet, or install the free software: Atomicwallet, or: Exodus wallet, then receive and send to mine. My Bitcoin (BTC) address is: 13HAreeSVjLf3aueZXf9zmrS1FmvkF4opS Yes, that's how the address looks like, copy and paste my address, it's (cAsE-sEnSEtiVE). You are given not more than 3 days after you have opened this email. As I got access to this email account, I will know if this email has already been read. Everything will be carried out based on fairness. An advice from me, regularly change all your passwords to your accounts and update your device with newest security patches.

2 3

[ruby-dev:52168] [Ruby Feature#21616] date ライブラリを deprecatedさせたい
by jinroq (Jinroq SAITOH) 11 Oct '25

11 Oct '25

Issue #21616 has been reported by jinroq (Jinroq SAITOH). ---------------------------------------- Feature #21616: date ライブラリを deprecated させたい https://bugs.ruby-lang.org/issues/21616 * Author: jinroq (Jinroq SAITOH) * Status: Open ---------------------------------------- ### 概要 *date ライブラリが長期間メンテナンスされておらず、機能を time ライブラリに委譲して deprecated させたい* というお話が出ていると風の噂で耳にしましたが、どこまでを考えられているのかご意見をお聞きしたいです。 ### 確認事項 #### `Date._parse` を time に移植したい `Time._parse` なるものが実現できれば十分でしょうか？（それっぽく移植は[してみました](https://github.com/ruby/time/compare/m… #### `Date.strptime` を time に移植したい [date_strptime.c](https://github.com/ruby/date/blob/master/ext/date/date_str… をそのまま time に移植していいものでしょうか？「time に移植するならついでにこんな感じだと嬉しい」といった要望があったりするのでしょうか？ #### deprecated させた場合の影響範囲 deprecated はかなりのインパクトであり、様々な gem やプロダクトに影響を及ぼすかと思います。例えば「Ruby on Rails では誰に相談すべきか」など、どこまでを考慮すべきでしょうか？ -- https://bugs.ruby-lang.org/

3 3

[ruby-dev:52164] [Ruby Bug#21608] 三項演算子と break を組み合わせると SyntaxError
by ursm (Keita Urashima) 17 Sep '25

17 Sep '25

Issue #21608 has been reported by ursm (Keita Urashima). ---------------------------------------- Bug #21608: 三項演算子と break を組み合わせると SyntaxError https://bugs.ruby-lang.org/issues/21608 * Author: ursm (Keita Urashima) * Status: Open * ruby -v: ruby 3.4.6 (2025-09-16 revision dbd83256b1) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ``` >> RUBY_VERSION => "3.4.5" >> [1, 2].find {|i| i.even? ? break i : nil } ``` ``` >> RUBY_VERSION => "3.4.6" >> [1, 2].find {|i| i.even? ? break i : nil } <internal:kernel>:168:in 'Kernel#loop': (irb):2: syntax error found (SyntaxError) > 2 | ... i : nil } | ^ unexpected local variable or method, expecting end-of-input from /home/ursm/.local/share/mise/installs/ruby/3.4.6/lib/ruby/gems/3.4.0/gems/irb-1.15.2/exe/irb:9:in '<top (required)>' from /home/ursm/.local/share/mise/installs/ruby/3.4.6/bin/irb:25:in 'Kernel#load' from /home/ursm/.local/share/mise/installs/ruby/3.4.6/bin/irb:25:in '<main>' ``` -- https://bugs.ruby-lang.org/

4 3

[ruby-dev:52162] 協力オファー
by ruby-dev＠ruby-lang.org 13 Jul '25

13 Jul '25

御機嫌よう！ ご覧の通り、これは形式張ったメールではありませんが、残念ながら何かあなたへの朗報だとも限りません。しかし、そんなことは重要ではないので落胆しないでくださいね。今から全てをご説明いたします。 私は、あなたが頻繁に利用されているローカルネットワークの一部となる電子デバイスにアクセスしました。あなたのアクティビティを過去数ヶ月間追跡しております。 どうしてこうなったのか？と言うことですが、 エクスプロイトによってハッキングされたウェブサイトへあなたが訪問した為、あなたのデバイスが、私のマルウェアに晒されたのがきっかけです。（マルウェアは、この分野の専門家からダークネットで購入しました。） これはとても複雑なソフトウェアで、トロイの木馬のように機能します。頻繁に更新される為、あなたのウィルス対策では検出できません。 このプログラムにはキーロガーが備わっていて、あなたのカメラやマイクのON/OFFを切り替えたり、ファイルを送信したり、あなたのローカルネットワークへのアクセスの提供を可能にします。 他のデバイスからの情報へアクセスするには少し時間を要しましたが、今のところ、私はあなたの全ての連絡先と会話内容、あなたの居場所についての情報、あなたが好きなもの、あなたのお気に入りのWebサイト等を把握しています。 正直な話、最初は何も悪気はなく、ただ楽しむために行っていました。これは私の趣味なのです。 しかしCOVIDに感染してしまい、残念ながら職を失いました。 そして、「自分の趣味」を使ってあなたからお金を頂戴する方法を考えついたのです！ あなたが自慰行為している動画を録画しました。この動画は二画面になっていて、あなたの顔は簡単に認識できますし、どのようなビデオを好むのかがハッキリと明らかになるようになっています。 私はこの行為を誇らしくは思っていないのですが、生き延びるためにはお金が必要なのです。 では、取引をしましょう。私が求める金額をあなたが私に支払えば、この動画があなたの友達、家族や他の知人に送信されることは一切ありません。 これは冗談ではないことは理解してくださいね。私はEメールで送信することもできますし、SMSのリンク、ソーシャルメディアを通して送信することも、マスメディアに投稿することもできるのです。（実はマスメディアの管理ページもハッキングしたんですよ。） だから、あなたはTwitterや米国メディアInstagramの「スター」になれるでしょう！ これを避けたければ、私のBTCウォレットに1,490 USD相当のビットコインを送金してください:1KDhJpD3izxHGj984vraGYbsiN1dDqaf1H ビットコインの使い方が分からなければ、BingやGoogleで＜ビットコインの購入方法＞等と検索すれば分かるはずです。 お金を受け取るとすぐに動画を削除します。その上、あなたのデバイスに感染したマルウェアも削除し、私から連絡を取ることは２度とありません。 ２日間を猶予としますが、それだけあれば十分なはずです。このメールを開くとすぐに時間追跡が始まります。私は状況を監視していますよ！ そして最後に、 私はTORを使用しているので、ビットコイン取引を追跡することは不可能なため、この事を警察に連絡しても意味はありません。 私に返信もしないでください。（このレターはあなたのアカウント内で作成し、この件に全く関係のない人物の本物のアドレスを添えています。）なので、私を追跡することは不可能です。 何か馬鹿げた事をしたり、私の期待に反するような事をしたりすれば、すぐにこの動画をシェアします。 幸運を祈ります！

1 0

[ruby-dev:52159] [Ruby Feature#21393] One-line pattern matching syntax as a method argument
by koic (Koichi ITO) 02 Jun '25

02 Jun '25

Issue #21393 has been reported by koic (Koichi ITO). ---------------------------------------- Feature #21393: One-line pattern matching syntax as a method argument https://bugs.ruby-lang.org/issues/21393 * Author: koic (Koichi ITO) * Status: Open ---------------------------------------- ## Context Using one-line `in` pattern matching syntax as a method argument causes a syntax error. ```console $ ruby -vce 'do_something(expression in pattern)' ruby 3.4.4 (2025-05-14 revision a38531fd3f) +PRISM [x86_64-darwin24] ruby: -e:1: syntax errors found (SyntaxError) > 1 | do_something(expression in pattern) | ^~ unexpected 'in'; expected a `)` to close the arguments | ^ unexpected ')', ignoring it | ^ unexpected ')', expecting end-of-input ``` Wrapping the argument in parentheses avoids the syntax error: ```console $ ruby -vce 'do_something((expression in pattern))' ruby 3.4.4 (2025-05-14 revision a38531fd3f) +PRISM [x86_64-darwin24] Syntax OK ``` This was unexpected, as I assumed `do_something(expression in pattern)` would work without parentheses. For reference, `do_something(expression => pattern)`, which results in a void context, is valid syntax. ```console $ ruby -vce 'do_something(expression => pattern)' ruby 3.4.4 (2025-05-14 revision a38531fd3f) +PRISM [x86_64-darwin24] Syntax OK ``` ## Proposal It seems more appropriate that `do_something(expression in pattern)` should also be valid syntax. ## Additional Information This behavior is consistent not only in Prism, but also in `parse.y`. ```console $ ruby --parser=parse.y -vce 'do_something(expression in pattern)' ruby 3.4.4 (2025-05-14 revision a38531fd3f) [x86_64-darwin24] -e:1: syntax error, unexpected 'in', expecting ')' do_something(expression in pattern) ruby: compile error (SyntaxError) ``` I encountered this while working on a RuboCop issue: https://github.com/rubocop/rubocop/issues/14217 -- https://bugs.ruby-lang.org/

2 2

[ruby-dev:52158] [Ruby Feature#14916] Proposal to add Array#===
by matheusrich (Matheus Richard) 16 May '25

16 May '25

Issue #14916 has been updated by matheusrich (Matheus Richard). This is probably unnecessary now that pattern matching exists. ---------------------------------------- Feature #14916: Proposal to add Array#=== https://bugs.ruby-lang.org/issues/14916#change-113306 * Author: osyo (manga osyo) * Status: Open ---------------------------------------- ## 概要 `Array#===` を追加する提案になります。基本的な動作は『`Array#==` の `===` で比較する版』になります。 ## 仕様配列の各要素をそれぞれ順に `===` で比較し、全要素が `true` の場合に `true` を返す。そうでない場合は `false` を返す。 ### 動作例 ```ruby # 配列の各要素を #=== を使用して比較する [ String, /\w/ ] === [ "a", "c", 7 ] # => false [ String, /\w/, (1..10) ] === [ "a", "c", 7 ] # => true [ String, /\w/, (1..10) ] === [ "a", "!", 42 ] # => false ``` ### 真を返すケース * レシーバと引数が配列で同じサイズかつ、各要素を `===` で比較したときに全て `true` になる場合 * レシーバと引数が同じオブジェクトの場合 ### 偽を返すケース * レシーバと引数が配列で同じサイズかつ、各要素を `===` で比較したときに `false` がある場合 * レシーバと引数の配列のサイズが異なる場合 * 引数が配列以外の場合 ## ユースケース ### 引数の値によって処理を変える可変長引数で引数を受け取り、そのまま case-when で値を精査する ```ruby def plus *args case args # 数値の場合 when [Integer, Integer] args[0] + args[1] # 数字の場合 when [/^\d+$/, /^\d+$/] args[0].to_i + args[1].to_i # それ以外はエラー else raise "Error" end end p plus 1, 2 # => 3 p plus "3", "4" # => 7 p plus "homu", "mado" # Error (RuntimeError) ``` ### FizzBuzz を用いた例任意の処理の結果を複数回参照したい場合、配列でまとめて case-when で利用する ```ruby def fizzbuzz n _ = proc { true } case [n % 3, n % 5] # n % 3 === 0 && n % 5 === 0 when [0, 0] "FizzBuzz" # n % 3 === 0 when [0, _] "Fizz" # n % 5 === 0 when [_, 0] "Buzz" else n end end p (1..20).map &method(:fizzbuzz) # => [1, 2, "Fizz", 4, "Buzz", "Fizz", 7, 8, "Fizz", "Buzz", 11, "Fizz", 13, 14, "FizzBuzz", 16, 17, "Fizz", 19, "Buzz"] ``` ## 関連しそうなチケット * [Feature #14869: Proposal to add Hash#=== - Ruby trunk - Ruby Issue Tracking System](https://bugs.ruby-lang.org/issues/14869?next_issue_id=14866&prev_is… * [Feature #14913: Extend case to match several values at once - Ruby trunk - Ruby Issue Tracking System](https://bugs.ruby-lang.org/issues/14913) 以上、 `Array#===` に関する提案になります。挙動に関して疑問点や意見などございましたらコメント頂けると助かります。 ---Files-------------------------------- array_eqq.patch (3.06 KB) array_eqq.patch (3.2 KB) array_eqq.patch (3.41 KB) -- https://bugs.ruby-lang.org/

1 0

[ruby-dev:52155] [Ruby Bug#21278] configureスクリプトが検出するruby_versionの値に'+0'が付く
by yasuhirokimura (Yasuhiro KIMURA) 21 Apr '25

21 Apr '25

Issue #21278 has been reported by yasuhirokimura (Yasuhiro KIMURA). ---------------------------------------- Bug #21278: configureスクリプトが検出するruby_versionの値に'+0'が付く https://bugs.ruby-lang.org/issues/21278 * Author: yasuhirokimura (Yasuhiro KIMURA) * Status: Open * ruby -v: ruby 3.5.0preview1 (2025-04-18 master d06ec25be4) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- # 再現手順 1. ruby-3.5.0-preview1.tar.xzをダウンロード 2. tar xfpvJ ruby-3.5.0-preview1.tar.xz 3. cd ruby-3.5.0-preview1 4. ./configure 5. fgrep ruby_version= config.log # 期待される結果 ``` % fgrep ruby_version= config.log ruby_version='3.5.0' % ``` # 実際に得られる結果 ``` % fgrep ruby_version= config.log ruby_version='3.5.0+0' % ``` 上記の手順4を`./configure --with-ruby-version=minor`にした場合にも同様の結果(ruby_versionの最後に"+0"が付く)となる # 環境以下の環境で問題が発生することを確認済 * Debian 12.10 amd64 * FreeBSD 14.2-RELEASE amd64 -- https://bugs.ruby-lang.org/

2 2