September 2024 - ruby-core - ml.ruby-lang.org

[ruby-core:111247] [Ruby master Feature#19191] Implicit console input transcoding is more desirable
by YO4 (Yoshinao Muramatsu) 22 Nov '24

22 Nov '24

Issue #19191 has been reported by YO4 (Yoshinao Muramatsu). ---------------------------------------- Feature #19191: Implicit console input transcoding is more desirable https://bugs.ruby-lang.org/issues/19191 * Author: YO4 (Yoshinao Muramatsu) * Status: Open * Priority: Normal ---------------------------------------- In response to Bug #18353, STDIN.internal_encoding are set and encoding is converted explcitly on Windows platform. For example, ```[STDIN.external_encoding, STDIN.internal_encoding] # => [Encoding::Windows-31J, Encoding::UTF-8]``` if STDIN is console. I feel that internal_encoding should be reserved for specific applications. And I think setting internal_encoding to STDIN is not foreseened. Today I found irb breaks STDIN encoding, like ``` >ruby -rirb -e "p [$stdin.external_encoding, $stdin.internal_encoding]; IRB.setup(''); IRB::Irb.new(); p [$stdin.external_encoding, $stdin.internal_encoding]" [#<Encoding:Windows-31J>, #<Encoding:UTF-8>] [#<Encoding:UTF-8>, nil] ``` We know input has console code page encoding. So we always can convert encoding from console code page to io_input_encoding(). ### proposal when reading from console on Windows, input encoding is enfoced to console code page and encoding conversion is implicitly applied. when ```set_encoding("UTF-8")``` implicitly converts console code page to UTF-8. when ```set_encoding("CP437", "UTF-8")``` implicitly converts console code page to UTF-8. external_encoding is ignored. binmode or binary input method is not affected by these specifications. set_encoding, etc. will continue to work as before, and this specification will affect only when encoding conversion on read (NEED_READCONV() and make_readconv()). -- https://bugs.ruby-lang.org/

2 5

[ruby-core:113489] [Ruby master Bug#19642] Remove vectored read/write from `io.c`.
by ioquatix (Samuel Williams) 20 Nov '24

20 Nov '24

Issue #19642 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #19642: Remove vectored read/write from `io.c`. https://bugs.ruby-lang.org/issues/19642 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- https://github.com/socketry/async/issues/228#issuecomment-1546789910 is a comment from the kernel developer who tells us that `writev` is always worse than `write` system call. A large amount of complexity in `io.c` comes from optional support from `writev`. So, I'd like to remove support for `writev`. I may try to measure the performance before/after. However it may not show much difference, except that the implementation in `io.c` can be much simpler. -- https://bugs.ruby-lang.org/

5 9

[ruby-core:111966] [Ruby master Feature#19366] Rename/alias Refinedment#refined_class => #refined_module
by zverok (Victor Shepelev) 19 Nov '24

19 Nov '24

Issue #19366 has been reported by zverok (Victor Shepelev). ---------------------------------------- Feature #19366: Rename/alias Refinedment#refined_class => #refined_module https://bugs.ruby-lang.org/issues/19366 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal ---------------------------------------- In #12737, `Refinement#refined_class` is introduced. As "module" is more generic concept than "class", the name misleadingly implies that either this method doesn't returns refined _modules_, or modules can't be refined. This is obviously not true and trivially disproved: ```ruby module Refs refine Enumerable do def foo = puts 'foo' end end Refs.refinements[0].refined_class #=> Enumerable. Which is, well, not a class. # The refinement is usable, so it is not a mute concept: using Refs [1, 2, 3].foo # prints "foo" successfully ``` I believe we refer to "modules" when some feature applies to modules and classes. Unless there is some deeper consideration for the current naming (I don't see justification in #12737, but I might miss something), the method should be renamed or aliased. PS: Sorry for a huge amount of "nitpicky" issues after the version release. Typically, those concerns emerge while I am working on the [changelog](https://rubyreferences.github.io/rubychanges/), and I am usually trying to start the work at least a month before the release. Unfortunately, due to you-know-what, I was unable to do it in time this year. After the 3.2 changelog, I plan to switch to the "master changelog" approach (following the development with the "current unreleased changes" document) this year. Unless I'll be unable to due to reasons not in my control. -- https://bugs.ruby-lang.org/

4 3

[ruby-core:117240] [Ruby master Feature#20350] Return chilled string from Symbol#to_s
by Dan0042 (Daniel DeLorme) 12 Nov '24

12 Nov '24

Issue #20350 has been reported by Dan0042 (Daniel DeLorme). ---------------------------------------- Feature #20350: Return chilled string from Symbol#to_s https://bugs.ruby-lang.org/issues/20350 * Author: Dan0042 (Daniel DeLorme) * Status: Open ---------------------------------------- During Ruby 2.7 development there was an attempt to return a frozen string from Symbol#to_s (#16150#note-22) This had to be rolled back due to incompatibility, but now we have chilled strings (#20205) Symbol#to_s can safely return a chilled string, giving developers time to fix warnings before switching to a frozen string. -- https://bugs.ruby-lang.org/

6 9

[ruby-core:118976] [Ruby master Bug#20704] Windows: `-C` option does not work for multibyte path name
by nobu (Nobuyoshi Nakada) 08 Nov '24

08 Nov '24

Issue #20704 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Bug #20704: Windows: `-C` option does not work for multibyte path name https://bugs.ruby-lang.org/issues/20704 * Author: nobu (Nobuyoshi Nakada) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Related to [Bug #20699]. ``` C:> \Ruby33-x64\bin\ruby.exe -C xテスト_test -ep \Ruby33-x64\bin\ruby.exe: Can't chdir to xテスト_test (fatal) ``` -- https://bugs.ruby-lang.org/

4 4

[ruby-core:119050] [Ruby master Feature#20715] `Ractor.[]` and `Ractor.[]=` to access Ractor local storage
by ko1 (Koichi Sasada) 06 Nov '24

06 Nov '24

Issue #20715 has been reported by ko1 (Koichi Sasada). ---------------------------------------- Feature #20715: `Ractor.[]` and `Ractor.[]=` to access Ractor local storage https://bugs.ruby-lang.org/issues/20715 * Author: ko1 (Koichi Sasada) * Status: Open * Assignee: ko1 (Koichi Sasada) ---------------------------------------- Trivial proposal. Now `Ractor#[]/#[]=` is supported to access current ractor local storage. However, it doesn't allow to access local storage of other ractors. ```ruby Ractor.current[:foo] = 1 Ractor.new{ p Ractor.main[:foo] #=> nil }.take ``` So providing `Ractor.[]/[]=` is more reasonable. Further more, we don't need to use `Ractor#current` and it is slightly faster. -- https://bugs.ruby-lang.org/

4 3

[ruby-core:119208] [Ruby master Bug#20745] IO::Buffer#copy triggers UB when src/dest buffers overlap
by hanazuki (Kasumi Hanazuki) 06 Nov '24

06 Nov '24

Issue #20745 has been reported by hanazuki (Kasumi Hanazuki). ---------------------------------------- Bug #20745: IO::Buffer#copy triggers UB when src/dest buffers overlap https://bugs.ruby-lang.org/issues/20745 * Author: hanazuki (Kasumi Hanazuki) * Status: Open * ruby -v: ruby 3.4.0dev (2024-09-15T01:06:11Z master 532af89e3b) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- The current implementation of `IO::Buffer#copy` uses `memcpy` to copy data between the two memory regions. `memcpy` has a requirement that the source and destination must not overlap; otherwise the behavior is undefined. When copying between the same instance of `IO::Buffer` (or slices sharing the same underlying memory), the rule can be violated, and the data is corrupted with some libc implementation / architecture combinations (note that Alpine uses musl libc). ```shell-session % docker run --platform=linux/amd64 --rm ruby:3.3.5-alpine3.20 ruby -e 'b=IO::Buffer.new(10); b.set_string("0123456789"); b.copy(b, 3, 7, 0); p b' -e:1: warning: IO::Buffer is experimental and both the Ruby and C interface may change in the future! #<IO::Buffer 0x00007fb439d2c450+10 INTERNAL> 0x00000000 30 31 32 30 31 32 30 31 32 30 0120120120 % docker run --platform=linux/arm64 --rm ruby:3.3.5-alpine3.20 ruby -e 'b=IO::Buffer.new(10); b.set_string("0123456789"); b.copy(b, 3, 7, 0); p b' -e:1: warning: IO::Buffer is experimental and both the Ruby and C interface may change in the future! #<IO::Buffer 0x00007fcc5c580360+10 INTERNAL> 0x00000000 30 31 32 30 31 32 33 34 35 36 0120123456 ``` Copying "0123456789" three bytes behind onto itself, "0120123456" is the expected result. --- This error can also be detected with ASAN. ```shell-session % CXX=clang++ CC=clang ./configure cppflags="-fsanitize=address -fno-omit-frame-pointer" optflags=-O0 LDFLAGS="-fsanitize=address -fno-omit-frame-pointer" % ./ruby -e 'b=IO::Buffer.new(10); b.copy(b, 0, 9, 1)' `RubyGems' were not loaded. `error_highlight' was not loaded. `did_you_mean' was not loaded. `syntax_suggest' was not loaded. -e:1: warning: IO::Buffer is experimental and both the Ruby and C interface may change in the future! ================================================================= ==1655425==ERROR: AddressSanitizer: memcpy-param-overlap: memory ranges [0x5020000107b0,0x5020000107b9) and [0x5020000107b1, 0x5020000107ba) overlap #0 0x55dcfbb72d90 in __asan_memcpy (/home/kasumi/.local/src/github.com/ruby/ruby/ruby+0x1fdd90) (BuildId: 2591ca8e9e713537a8f388383df19d1f4284b722) #1 0x55dcfbcb31e3 in ruby_nonempty_memcpy /home/kasumi/.local/src/github.com/ruby/ruby/./include/ruby/internal/memory.h:662:16 #2 0x55dcfbcb3867 in io_buffer_memcpy /home/kasumi/.local/src/github.com/ruby/ruby/io_buffer.c:2347:5 #3 0x55dcfbcb354a in io_buffer_copy_from /home/kasumi/.local/src/github.com/ruby/ruby/io_buffer.c:2384:5 #4 0x55dcfbcafd2f in io_buffer_copy /home/kasumi/.local/src/github.com/ruby/ruby/io_buffer.c:2490:12 #5 0x55dcfc0b955f in ractor_safe_call_cfunc_m1 /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:3597:12 #6 0x55dcfc09ca28 in vm_call_cfunc_with_frame_ /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:3788:11 #7 0x55dcfc09cf2a in vm_call_cfunc_with_frame /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:3834:12 #8 0x55dcfc09c0e9 in vm_call_cfunc_other /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:3860:16 #9 0x55dcfc081811 in vm_call_cfunc /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:3942:12 #10 0x55dcfc07f347 in vm_call_method_each_type /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:4766:16 #11 0x55dcfc07ebc2 in vm_call_method /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:4892:20 #12 0x55dcfc02d9a4 in vm_call_general /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:4936:12 #13 0x55dcfc02fb24 in vm_sendish /home/kasumi/.local/src/github.com/ruby/ruby/./vm_insnhelper.c:5955:15 #14 0x55dcfc03eb00 in vm_exec_core /home/kasumi/.local/src/github.com/ruby/ruby/insns.def:898:11 #15 0x55dcfc0306a2 in rb_vm_exec /home/kasumi/.local/src/github.com/ruby/ruby/vm.c:2564:22 #16 0x55dcfc06ee9f in rb_iseq_eval_main /home/kasumi/.local/src/github.com/ruby/ruby/vm.c:2830:11 #17 0x55dcfbbb7a84 in rb_ec_exec_node /home/kasumi/.local/src/github.com/ruby/ruby/eval.c:281:9 #18 0x55dcfbbb74b2 in ruby_run_node /home/kasumi/.local/src/github.com/ruby/ruby/eval.c:319:30 #19 0x55dcfbbaf81e in rb_main /home/kasumi/.local/src/github.com/ruby/ruby/./main.c:43:12 #20 0x55dcfbbaf699 in main /home/kasumi/.local/src/github.com/ruby/ruby/./main.c:62:12 #21 0x7fb604914db9 in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 #22 0x7fb604914e74 in __libc_start_main csu/../csu/libc-start.c:360:3 #23 0x55dcfbad8fe0 in _start (/home/kasumi/.local/src/github.com/ruby/ruby/ruby+0x163fe0) (BuildId: 2591ca8e9e713537a8f388383df19d1f4284b722) [snip] ``` -- https://bugs.ruby-lang.org/

5 7

[ruby-core:119250] [Ruby master Bug#20753] [doc] IO::Buffer examples try to write into readonly buffer returned from IO::Buffer.for
by hanazuki (Kasumi Hanazuki) 05 Nov '24

05 Nov '24

Issue #20753 has been reported by hanazuki (Kasumi Hanazuki). ---------------------------------------- Bug #20753: [doc] IO::Buffer examples try to write into readonly buffer returned from IO::Buffer.for https://bugs.ruby-lang.org/issues/20753 * Author: hanazuki (Kasumi Hanazuki) * Status: Open * ruby -v: ruby 3.4.0dev (2024-09-18T02:16:22Z master 4797b0704a) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- `IO::Buffer.for` without a block returns a readonly `IO::Buffer`. Some examples in the documentation for `IO::Buffer` write into the readonly buffers, which actually raise an `IO::Buffer::AccessError`. From `IO::Buffer#clear`: > ``` > buffer = IO::Buffer.for('test') > # => > # <IO::Buffer 0x00007fca40087c38+4 SLICE> > # 0x00000000 74 65 73 74 test > > buffer.clear > # => > # <IO::Buffer 0x00007fca40087c38+4 SLICE> > # 0x00000000 00 00 00 00 .... > ``` From `IO::Buffer#copy`: > ``` > string= "data: " > # => "data: " > buffer = IO::Buffer.for(string) > buffer.copy(IO::Buffer.for("test"), 5) > # => 4 > ``` And `IO::Buffer#slice`, which should be fixed along with its implementation #20752 -- https://bugs.ruby-lang.org/

3 3

[ruby-core:119312] [Ruby master Bug#20762] `make test-basic` with -DRGENGC_FORCE_MAJOR_GC is always failure
by hsbt (Hiroshi SHIBATA) 05 Nov '24

05 Nov '24

Issue #20762 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #20762: `make test-basic` with -DRGENGC_FORCE_MAJOR_GC is always failure https://bugs.ruby-lang.org/issues/20762 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- https://github.com/ruby/ruby/actions/runs/11063957302/job/30741993035#step:… ---- ``` /github/workspace/src/basictest/test.rb:2357: [BUG] cannot create a new page after major GC ruby 3.4.0dev (2024-09-27T03:22:52Z pull/11217/merge cfa3f15e14) +PRISM [x86_64-linux] -- Control frame information ----------------------------------------------- c:0004 p:0004 s:0057 e:000055 BLOCK /github/workspace/src/basictest/test.rb:2357 [FINISH] self: (embed) len:3 lvars: o: (String) len: 7, capa: 15 "select!" c:0003 p:---- s:0052 e:000051 CFUNC :each_object me: called_id: each_object, type: cfunc owner class: (anon) self: ObjectSpace c:0002 p:15612 s:0048 E:002140 EVAL /github/workspace/src/basictest/test.rb:2356 [FINISH] self: (embed) len:3 lvars: a: T_FIXNUM 1 h: (Hash)[A] 1 aa: T_FIXNUM 5 bb: T_FIXNUM 25 cc: T_FIXNUM 44 b: (Binding)binding c: T_FIXNUM 3 f: (Foo)(embed) len:3 x: (Alias3)(embed) len:3 y: T_FIXNUM 2 z: T_NIL while_tmp: (String) len: 15, capa: 55 "while_tmp.52326" tmp: T_NIL line: (String) len: 7, capa: 15 "tvi925 " lastline: (String) len: 6, capa: 15 "paper " sum: T_FIXNUM 220 i: T_FIXNUM 5 e: (RuntimeError)(embed) len:8 k: T_FIXNUM 3 v: T_FIXNUM 6 done: T_TRUE m: (MatchData) blk: (Proc) block in <main>@/github/workspace/src/basictest/test.rb:1207 lmd: (Proc) block in <main>@/github/workspace/src/basictest/test.rb:1213 nan: (Float) n1: (Integer) n2: (Integer) foo: T_FIXNUM 5 s: (String) len: 6, capa: 15 "1,2,3 " d: T_FIXNUM 4 p1: (Binding)binding i7: T_NIL script_tmp: (String) len: 16, capa: 55 "script_tmp.52326" bar: (embed) len:3 ary: (Array)[E ] len: 11 (embed) ary2: (Array)[ ] len: 11, capa:20 ptr:0x000055c64bd8e960 struct_test: Struct::Test test: (Struct::Test) foobar: (String) len: 6, capa: 15 "foobar" atlas: (Titans)(embed) len:3 dosish: T_NIL l: (Array)[ ] len: 100000, capa:127694 ptr:0x00007fb4d72ea010 c:0001 p:0000 s:0003 E:0012a0 DUMMY [FINISH] self: (embed) len:3 -- Ruby level backtrace information ---------------------------------------- /github/workspace/src/basictest/test.rb:2356:in '<main>' /github/workspace/src/basictest/test.rb:2356:in 'each_object' /github/workspace/src/basictest/test.rb:2357:in 'block in <main>' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 1 -- C level backtrace information ------------------------------------------- /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_print_backtrace+0x14) [0x7fb4f2db5e3c] /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm_dump.c:822 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_vm_bugreport) /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm_dump.c:1151 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_bug_without_die+0xe8) [0x7fb4f2c01318] /tmp/tmp.WEBb0YaZEC//github/workspace/src/error.c:1084 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_bug+0x80) [0x7fb4f2b506d3] /tmp/tmp.WEBb0YaZEC//github/workspace/src/error.c:1092 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(newobj_cache_miss+0x4bf) [0x7fb4f2c2381f] /github/workspace/src/gc/default.c:2169 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(newobj_of+0x264) [0x7fb4f2c18f04] /github/workspace/src/gc/default.c:2478 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_wb_protected_newobj_of+0x25) [0x7fb4f2c18f55] /tmp/tmp.WEBb0YaZEC//github/workspace/src/gc.c:917 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_cc_new+0xd) [0x7fb4f2d869d3] /github/workspace/src/vm_callinfo.h:334 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_search_cc) /github/workspace/src/vm_insnhelper.c:2177 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_vm_search_method_slowpath) /github/workspace/src/vm_insnhelper.c:2196 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_search_method_slowpath0+0x8) [0x7fb4f2d8c7c6] /github/workspace/src/vm_insnhelper.c:2217 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_search_method_fastpath) /github/workspace/src/vm_insnhelper.c:2278 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_sendish) /github/workspace/src/vm_insnhelper.c:5954 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_exec_core) /tmp/tmp.WEBb0YaZEC/insns.def:898 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_exec_loop+0x0) [0x7fb4f2d88dc6] /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:2564 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_vm_exec) /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:2567 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(invoke_block_from_c_bh+0x3cb) [0x7fb4f2db01cb] /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:1595 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_yield_with_cref+0x45) [0x7fb4f2d97ca5] /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:1646 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_yield) /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:1654 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_yield_0) /github/workspace/src/vm_eval.c:1344 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_yield) /github/workspace/src/vm_eval.c:1360 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(os_obj_of_i+0x38) [0x7fb4f2c2b438] /tmp/tmp.WEBb0YaZEC//github/workspace/src/gc.c:1372 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(objspace_each_objects_try+0x135) [0x7fb4f2c29995] /github/workspace/src/gc/default.c:2772 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_ensure+0xe1) [0x7fb4f2c0ac81] /tmp/tmp.WEBb0YaZEC//github/workspace/src/eval.c:1053 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(objspace_each_objects+0xa3) [0x7fb4f2c2222a] /github/workspace/src/gc/default.c:2803 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_gc_impl_each_objects) /github/workspace/src/gc/default.c:2822 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_objspace_each_objects) /tmp/tmp.WEBb0YaZEC//github/workspace/src/gc.c:2885 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(os_each_obj) /tmp/tmp.WEBb0YaZEC//github/workspace/src/gc.c:1389 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_cfp_consistent_p+0x0) [0x7fb4f2da7e02] /github/workspace/src/vm_insnhelper.c:3788 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_call_cfunc_with_frame_) /github/workspace/src/vm_insnhelper.c:3790 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(RB_UNDEF_P+0x0) [0x7fb4f2d8bfe4] /github/workspace/src/vm_insnhelper.c:5955 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_exec_core) /tmp/tmp.WEBb0YaZEC/insns.def:852 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(vm_exec_loop+0xac) [0x7fb4f2d88d34] /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:2591 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_vm_exec) /tmp/tmp.WEBb0YaZEC//github/workspace/src/vm.c:2570 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(rb_ec_exec_node+0x3a) [0x7fb4f2c09cd4] /tmp/tmp.WEBb0YaZEC//github/workspace/src/eval.c:281 /tmp/tmp.WEBb0YaZEC/libruby.so.3.4(ruby_run_node) /tmp/tmp.WEBb0YaZEC//github/workspace/src/eval.c:319 /tmp/tmp.WEBb0YaZEC/ruby(rb_main+0x1c) [0x55c64a844249] /tmp/tmp.WEBb0YaZEC//github/workspace/src/main.c:43 /tmp/tmp.WEBb0YaZEC/ruby(main) /tmp/tmp.WEBb0YaZEC//github/workspace/src/main.c:62 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_call_main+0x80) [0x7fb4f27bed90] ../sysdeps/nptl/libc_start_call_main.h:58 /lib/x86_64-linux-gnu/libc.so.6(call_init+0x0) [0x7fb4f27bee40] ../csu/libc-start.c:392 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main_impl) ../csu/libc-start.c:379 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main) (null):0 /tmp/tmp.WEBb0YaZEC/ruby(_start) [0x55c64a8440f5] (snip) ``` -- https://bugs.ruby-lang.org/

4 5

[ruby-core:119074] [Ruby master Bug#20716] Different instance_method behavior in Ruby 2.7 and Ruby 3.x
by natton (Tien Truong) 04 Nov '24

04 Nov '24

Issue #20716 has been reported by natton (Tien Truong). ---------------------------------------- Bug #20716: Different instance_method behavior in Ruby 2.7 and Ruby 3.x https://bugs.ruby-lang.org/issues/20716 * Author: natton (Tien Truong) * Status: Open * ruby -v: 3.3.1 * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Hi, I am working on upgrading our project from 2.7 to 3.x and found a breaking change in `instance_method` behavior. Here is the code snippet ``` module A def test(*args) super end end module B def test(a) puts a end end B.prepend(A) a = lambda do puts 'lambda' end class C include B end B.instance_method(:test).bind(C.new).call(1) # Ruby 2.7: 1 # Ruby 3.0: 1 # Ruby 3.1: 1 B.module_exec do define_method(:test, a) end B.instance_method(:test).bind(C.new).call # Ruby 2.7: lambda # Ruby 3.0: wrong number of arguments (given 0, expected 1) (ArgumentError) # Ruby 3.1: wrong number of arguments (given 0, expected 1) (ArgumentError) ``` I don't know if this is a bug or a correct intention. My specs: - Ruby manager: rbenv - Tested on - ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux] - ruby 3.0.7p220 (2024-04-23 revision 724a071175) [x86_64-linux] - ruby 3.1.4p223 (2023-03-30 revision 957bb7cb81) [x86_64-linux] - ruby 3.2.3 (2024-01-18 revision 52bb2ac0a6) [x86_64-linux] - ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linux] -- https://bugs.ruby-lang.org/

4 12