- ruby-core - ml.ruby-lang.org

[ruby-core:125150] [Ruby Bug#21970] Corrupted `ciobj->operands` in `compile.c: optimize_checktype`
by byroot (Jean Boussier) 30 Jun '26

30 Jun '26

Issue #21970 has been reported by byroot (Jean Boussier). ---------------------------------------- Bug #21970: Corrupted `ciobj->operands` in `compile.c: optimize_checktype` https://bugs.ruby-lang.org/issues/21970 * Author: byroot (Jean Boussier) * Status: Open * ruby -v: ruby 4.0.2 (2026-03-17 revision d3da9fec82) +PRISM [aarch64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- A rare crash I observed in production. I unfortunately don't have a reproduction, but perhaps this will ring a bell to someone. ``` #4 0x0000aaaac9afb1b8 [PAC] in sigsegv (sig=11, info=0xaaaaff573e30, ctx=0xaaaaff573eb0) at signal.c:948 #5 <signal handler called> #6 0x0000aaaac9ddcb60 in get_next_insn (iobj=0xffffffff00000001) at compile.c:3078 #7 optimize_checktype (iobj=0xaaab00000640, iseq=0xffff6e41ac80) at compile.c:3291 #8 iseq_peephole_optimize (iseq=iseq@entry=0xffff6e41ac80, list=list@entry=0xaaab00000640, do_tailcallopt=do_tailcallopt@entry=0) at compile.c:3363 #9 0x0000aaaac9dde590 [PAC] in iseq_optimize (anchor=<optimized out>, iseq=<optimized out>) at compile.c:4453 #10 iseq_setup_insn (anchor=<optimized out>, iseq=<optimized out>) at compile.c:1648 #11 iseq_setup_insn (iseq=0xffff6e41ac80, anchor=0xffffdb42d078) at compile.c:1637 #12 0x0000aaaac9e22d34 [PAC] in pm_iseq_compile_node (iseq=0xffff6e41ac80, node=<optimized out>) at /ruby-4.0.2/prism_compile.c:10514 #13 0x0000aaaac9a32f08 [PAC] in pm_iseq_new_with_opt_try (d=d@entry=281474360333120) at iseq.c:1106 #14 0x0000aaaac99c81bc [PAC] in rb_protect (proc=proc@entry=0xaaaac9a32eec <pm_iseq_new_with_opt_try>, data=data@entry=281474360333120, pstate=pstate@entry=0xffffdb42d3e4) at eval.c:1127 #15 0x0000aaaac9a39408 [PAC] in pm_iseq_new_with_opt (node=node@entry=0xffffdb42d510, name=name@entry=281472546599520, path=path@entry=281472531544280, realpath=281472531544280, first_lineno=first_lineno@entry=215, parent=parent@entry=0x0, isolated_depth=isolated_depth@entry=0, type=type@entry=ISEQ_TYPE_METHOD, option=0xffffdb42d328, error_state=error_state@entry=0xffffdb42d3e4) at iseq.c:1159 #16 0x0000aaaac9dcf1fc [PAC] in pm_new_child_iseq (iseq=iseq@entry=0xffff6e41b068, node=node@entry=0xffffdb42d510, name=281472546599520, parent=parent@entry=0x0, type=type@entry=ISEQ_TYPE_METHOD, line_no=215) at /ruby-4.0.2/iseq.h:154 #17 0x0000aaaac9e0688c [PAC] in pm_compile_node (iseq=iseq@entry=0xffff6e41b068, node=0xaaab000f0ac0, ret=ret@entry=0xffffdb42dcd8, popped=popped@entry=true, scope_node=scope_node@entry=0xffffdb42e170) at /ruby-4.0.2/prism_compile.c:9073 #18 0x0000aaaac9e0bd7c [PAC] in pm_compile_node (iseq=iseq@entry=0xffff6e41b068, node=0xaaab000eeed0, ret=ret@entry=0xffffdb42dcd8, popped=popped@entry=false, scope_node=scope_node@entry=0xffffdb42e170) at /ruby-4.0.2/prism_compile.c:10327 #19 0x0000aaaac9e1ee4c [PAC] in pm_compile_scope_node (iseq=iseq@entry=0xffff6e41b068, scope_node=scope_node@entry=0xffffdb42e170, ret=ret@entry=0xffffdb42dcd8, popped=popped@entry=false, node_location=<optimized out>, node_location=<optimized out>) at /ruby-4.0.2/prism_compile.c:7047 ``` ``` (gdb) f 7 #7 optimize_checktype (iobj=0xaaab00000640, iseq=0xffff6e41ac80) at compile.c:3291 3291 ciobj = (INSN *)get_next_insn((INSN*)OPERAND_AT(ciobj, 0)); (gdb) p (INSN*)ciobj->operands[0] $7 = (INSN *) 0xffffffff00000001 (gdb) p *(INSN*)ciobj->operands[0] Cannot access memory at address 0xffffffff00000001 ``` -- https://bugs.ruby-lang.org/

2 4

[ruby-core:125876] [Ruby Bug#18995] IO#set_encoding sometimes set an IO's internal encoding to the default external encoding
by javanthropus (Jeremy Bopp) 29 Jun '26

29 Jun '26

Issue #18995 has been updated by javanthropus (Jeremy Bopp). https://github.com/ruby/ruby/pull/17466 ---------------------------------------- Bug #18995: IO#set_encoding sometimes set an IO's internal encoding to the default external encoding https://bugs.ruby-lang.org/issues/18995#change-117803 * Author: javanthropus (Jeremy Bopp) * Status: Open * ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- This script demonstrates the behavior: ```ruby def show(io) printf( "external encoding: %-25p internal encoding: %-25p\n", io.external_encoding, io.internal_encoding ) end Encoding.default_external = 'iso-8859-1' Encoding.default_internal = 'iso-8859-2' File.open('/dev/null') do |f| f.set_encoding('utf-8', nil) show(f) # f.internal_encoding is iso-8859-2, as expected f.set_encoding('utf-8', 'invalid') show(f) # f.internal_encoding is now iso-8859-1! Encoding.default_external = 'iso-8859-3' Encoding.default_internal = 'iso-8859-4' show(f) # f.internal_encoding is now iso-8859-3! end ``` In the 1st case, we see that the IO's internal encoding is set to the current setting of Encoding.default_internal. In the 2nd case, the IO's internal encoding is set to Encoding.default_external instead. The 3rd case is more interesting because it shows that the IO's internal encoding is actually following the current setting of Encoding.default_external. It didn't just copy it when #set_encoding was called. It changes whenever Encoding.default_external changes. What should the correct behavior be? -- https://bugs.ruby-lang.org/

1 0

[ruby-core:125788] [Ruby Bug#22120] Segfault caused by ar_find_entry_hint() not checking for conversion to st_table
by Eregon (Benoit Daloze) 29 Jun '26

29 Jun '26

Issue #22120 has been reported by Eregon (Benoit Daloze). ---------------------------------------- Bug #22120: Segfault caused by ar_find_entry_hint() not checking for conversion to st_table https://bugs.ruby-lang.org/issues/22120 * Author: Eregon (Benoit Daloze) * Status: Open * Assignee: Eregon (Benoit Daloze) * Target version: 4.1 * ruby -v: ruby 4.1.0dev (2026-06-17T10:52:40Z master 0888fa8cb5) +PRISM [arm64-darwin25] * Backport: 3.3: UNKNOWN, 3.4: REQUIRED, 4.0: REQUIRED ---------------------------------------- While perusing code in hash.c (motivated by some crashes reported in https://github.com/DataDog/dd-trace-rb/issues/5718) I found it suspicious that `ar_find_entry_hint()` didn't reread `bound` in the loop and yet called arbitrary code through `#eql?`. Indeed, ar_find_entry_hint() does not check if bound or the storage (AR->ST) changed and would return a bin index which is not correct to access: ```c static unsigned ar_find_entry_hint(VALUE hash, ar_hint_t hint, st_data_t key) { unsigned i, bound = RHASH_AR_TABLE_BOUND(hash); const ar_hint_t *hints = RHASH_AR_TABLE(hash)->ar_hint.ary; /* if table is NULL, then bound also should be 0 */ for (i = 0; i < bound; i++) { if (hints[i] == hint) { ar_table_pair *pair = RHASH_AR_TABLE_REF(hash, i); if (ar_equal(key, pair->key)) { RB_DEBUG_COUNTER_INC(artable_hint_hit); return i; } else { RB_DEBUG_COUNTER_INC(artable_hint_miss); } } } RB_DEBUG_COUNTER_INC(artable_hint_notfound); return RHASH_AR_TABLE_MAX_BOUND; } ``` Fix: https://github.com/ruby/ruby/pull/17383 With the conversion from AR to ST it can actually trigger a segfault: This repro uses a single thread and mutates inside `eql?` for simplicity, but the same crash happens with another Thread mutating while the main Thread is in `eql?`. ```ruby class Key attr_reader :v def initialize(v, h = nil) @v = v @h = h end def hash = 0 def eql?(other) if @h # Trigger AR->ST conversion @h[42] = 42 end other.is_a?(Key) && @v == other.v end def inspect = "K(#{@v})" end h = {} 8.times { |i| h[Key.new(i)] = i } # Not in the hash, so ar_find_entry_hint checks every entry. lookup_key = Key.new(-1, h) p h[lookup_key] ``` ``` $ ./miniruby ar_find_entry_hint_bug.rb ar_find_entry_hint_bug.rb:15: [BUG] Segmentation fault at 0x0000000000000004 ruby 4.1.0dev (2026-06-17T10:52:40Z master 0888fa8cb5) +PRISM [arm64-darwin25] -- 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:0003 p:0021 s:0018 e:000015 l:y b:0001 r:0x0 METHOD ar_find_entry_hint_bug.rb:15 [FINISH] c:0002 p:0046 s:0011 E:0014e0 l:n b:---- r:0x0 EVAL ar_find_entry_hint_bug.rb:27 [FINISH] c:0001 p:0000 s:0003 E:002480 l:y b:---- r:0x0 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- ar_find_entry_hint_bug.rb:27:in '<main>' ar_find_entry_hint_bug.rb:15:in 'eql?' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 1 -- Machine register context ------------------------------------------------ x0: 0x0000000000000004 x1: 0x00000000000011bf x2: 0x000000016b9ed680 x3: 0x0000000000000000 x4: 0x0000000000000001 x5: 0x0000000000000001 x6: 0x0000000104d400a0 x7: 0xfffff0003ffff800 x18: 0x0000000000000000 x19: 0x000000016b9ed6d0 x20: 0x0000000104d41200 x21: 0x0000000000000000 x22: 0x00000000000011bf x23: 0x0000000000000000 x24: 0x0000000000000000 x25: 0x0000000104a96000 x26: 0x0000000000000009 x27: 0x0000000afd00aa00 x28: 0x0000000104a96000 lr: 0x00000001046a21dc fp: 0x000000016b9ed6c0 sp: 0x000000016b9ed680 -- C level backtrace information ------------------------------------------- /Users/benoit.daloze/code/ruby/miniruby(rb_vm_bugreport+0xbfc) [0x1046aec04] /Users/benoit.daloze/code/ruby/vm_dump.c:1473 /Users/benoit.daloze/code/ruby/miniruby(rb_vm_bugreport) (null):0 /Users/benoit.daloze/code/ruby/miniruby(rb_bug_for_fatal_signal+0x10c) [0x1044c7cd4] /Users/benoit.daloze/code/ruby/error.c:1140 /Users/benoit.daloze/code/ruby/miniruby(sigsegv+0x94) [0x1045ff93c] /Users/benoit.daloze/code/ruby/signal.c:948 /usr/lib/system/libsystem_platform.dylib(_sigtramp+0x38) [0x1891a57a4] /Users/benoit.daloze/code/ruby/miniruby(lookup_method_table+0x7c) [0x1046a21dc] ./vm_method.c:1363 /Users/benoit.daloze/code/ruby/miniruby(search_method0) ./vm_method.c:1822 /Users/benoit.daloze/code/ruby/miniruby(search_method+0x14) [0x104685960] ./vm_method.c:1845 /Users/benoit.daloze/code/ruby/miniruby(callable_method_entry_or_negative) ./vm_method.c:2049 /Users/benoit.daloze/code/ruby/miniruby(callable_method_entry+0x10) [0x104677fd0] ./vm_method.c:2078 /Users/benoit.daloze/code/ruby/miniruby(rb_callable_method_entry) ./vm_method.c:2085 /Users/benoit.daloze/code/ruby/miniruby(rb_vm_search_method_slowpath) ./vm_insnhelper.c:2039 /Users/benoit.daloze/code/ruby/miniruby(vm_search_method_slowpath0+0x8) [0x10467e6cc] ./vm_insnhelper.c:2214 /Users/benoit.daloze/code/ruby/miniruby(vm_exec_core) ./vm_insnhelper.c:2277 /Users/benoit.daloze/code/ruby/miniruby(vm_exec_loop+0x0) [0x10467a970] /Users/benoit.daloze/code/ruby/vm.c:2796 /Users/benoit.daloze/code/ruby/miniruby(rb_vm_exec) /Users/benoit.daloze/code/ruby/vm.c:2799 /Users/benoit.daloze/code/ruby/miniruby(rb_funcallv_scope+0x238) [0x10468a0c0] ./vm_eval.c:101 /Users/benoit.daloze/code/ruby/miniruby(rb_funcallv+0x8) [0x10468a4cc] ./vm_eval.c:1084 /Users/benoit.daloze/code/ruby/miniruby(rb_funcall) ./vm_eval.c:1141 /Users/benoit.daloze/code/ruby/miniruby(RB_TEST+0x0) [0x10455f248] /Users/benoit.daloze/code/ruby/object.c:161 /Users/benoit.daloze/code/ruby/miniruby(rb_eql) /Users/benoit.daloze/code/ruby/object.c:163 /Users/benoit.daloze/code/ruby/miniruby(rb_any_cmp+0xd0) [0x1044ff0e0] /Users/benoit.daloze/code/ruby/hash.c:138 /Users/benoit.daloze/code/ruby/miniruby(ar_equal+0xc) [0x104508328] /Users/benoit.daloze/code/ruby/hash.c:603 /Users/benoit.daloze/code/ruby/miniruby(ar_find_entry+0x54) [0x104500af4] /Users/benoit.daloze/code/ruby/hash.c:617 /Users/benoit.daloze/code/ruby/miniruby(ar_lookup) /Users/benoit.daloze/code/ruby/hash.c:1025 /Users/benoit.daloze/code/ruby/miniruby(rb_hash_aref) /Users/benoit.daloze/code/ruby/hash.c:2037 /Users/benoit.daloze/code/ruby/miniruby(vm_exec_core+0x4790) [0x104680c18] ./vm_insnhelper.c:6958 /Users/benoit.daloze/code/ruby/miniruby(vm_exec_loop+0x0) [0x10467a970] /Users/benoit.daloze/code/ruby/vm.c:2796 /Users/benoit.daloze/code/ruby/miniruby(rb_vm_exec) /Users/benoit.daloze/code/ruby/vm.c:2799 /Users/benoit.daloze/code/ruby/miniruby(rb_ec_exec_node+0xb4) [0x1044d317c] /Users/benoit.daloze/code/ruby/eval.c:284 /Users/benoit.daloze/code/ruby/miniruby(ruby_run_node+0x4c) [0x1044d3074] /Users/benoit.daloze/code/ruby/eval.c:322 /Users/benoit.daloze/code/ruby/miniruby(rb_main+0x1c) [0x104410980] ./main.c:42 /Users/benoit.daloze/code/ruby/miniruby(main) ./main.c:62 -- Other runtime information ----------------------------------------------- * Loaded script: ar_find_entry_hint_bug.rb * Ruby Box: disabled * Loaded features: 0 enumerator.so 1 monitor.so 2 thread.rb 3 fiber.so 4 rational.so 5 complex.so 6 pathname.so 7 ruby2_keywords.rb 8 set.rb ``` I can also repro on 3.2.11. Reproducing locally seems harder on 3.3, 3.4 and 4.0 but I believe they are affected too since they use very similar code and miss those checks, so we should backport there as well. Backporting to 3.2 may make sense too since this could be seen as a form of DoS. The repro depends on how the `ar_table` and `st_table` layouts overlap and specific values written & read. --- For completeness, I initially tried another repro, which shows unclear semantics but doesn't crash: ```ruby $break = false class Key def hash = 42 def eql?(o) if $break $break = false H.shift H[Key.new] = 42 until H.size == 8 o.equal?($key1) else equal?(o) end end end $key1 = key1 = Key.new key2 = Key.new key3 = Key.new h = { key1 => 1, key2 => 2 } H = h p h $break = true p h[key3] ``` ``` $ ./miniruby bug.rb {#<Key:0x0000000101041200> => 1, #<Key:0x0000000101041240> => 2} 2 ``` So reading a key considered `eql?` to `key1` returns the value for `key2`, that seems quite surprising. The underlying issue there is `ar_find_entry_hint()` returns an index but doesn't read the value, so the value is read after `eql?`, in which/during which the Hash may have changed. -- https://bugs.ruby-lang.org/

3 4

[ruby-core:125675] [Ruby Bug#22101] ASAN heap-use-after-free in rb_data_free after TypedData dfree frees dynamic rb_data_type_t
by rwstauner (Randy Stauner) 29 Jun '26

29 Jun '26

Issue #22101 has been reported by rwstauner (Randy Stauner). ---------------------------------------- Bug #22101: ASAN heap-use-after-free in rb_data_free after TypedData dfree frees dynamic rb_data_type_t https://bugs.ruby-lang.org/issues/22101 * Author: rwstauner (Randy Stauner) * Status: Open * Backport: 3.3: REQUIRED, 3.4: REQUIRED, 4.0: REQUIRED ---------------------------------------- `rb_data_free` currently calls `dfree` and then evaluates `RTYPEDDATA_EMBEDDABLE_P(obj)`. Since `RTYPEDDATA_EMBEDDABLE_P(obj)` reads `RTYPEDDATA_TYPE(obj)->flags`, this can become a use-after-free if an extension's `dfree` releases a dynamically allocated `rb_data_type_t`. This was observed under ASAN with `glib2` 4.3.6, where `cinfo_free` frees `cinfo->data_type`. I have a fix that simply caches the TypedData type and the embeddable/free decision before invoking `dfree`, matching the existing pattern of caching `dfree` and `RUBY_TYPED_FREE_IMMEDIATELY` before extension cleanup code runs: https://github.com/ruby/ruby/pull/17266 This is a small defensive fix and is suitable for backport because it avoids a shutdown-time ASAN heap-use-after-free without changing TypedData ownership semantics. -- https://bugs.ruby-lang.org/

2 4

[ruby-core:125612] [Ruby Bug#22092] `Array#sum` takes slow path, does not perform compensated summation of Float elements when init argument is a Float
by georgeclaghorn (George Claghorn) 29 Jun '26

29 Jun '26

Issue #22092 has been reported by georgeclaghorn (George Claghorn). ---------------------------------------- Bug #22092: `Array#sum` takes slow path, does not perform compensated summation of Float elements when init argument is a Float https://bugs.ruby-lang.org/issues/22092 * Author: georgeclaghorn (George Claghorn) * Status: Open * ruby -v: ruby 4.0.1 (2026-01-13 revision e04267a14b) +PRISM [arm64-darwin24] * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- ``` % time ruby -e 'puts Array.new(1_000_000_000, 0.1).sum' 100000000.0 ruby -e 'puts Array.new(1_000_000_000, 0.1).sum' 2.67s user 2.02s system 71% cpu 6.577 total % time ruby -e 'puts Array.new(1_000_000_000, 0.1).sum(0.0)' 99999998.74541782 ruby -e 'puts Array.new(1_000_000_000, 0.1).sum(0.0)' 22.72s user 1.80s system 96% cpu 25.332 total ``` Both the fast path and compensated summation are undocumented implementation details as far as I know, but this appears to be a possible oversight. -- https://bugs.ruby-lang.org/

3 2

[ruby-core:125252] [Ruby Bug#21996] Crash when modifying instance variables during inspect or Marshal dump
by jhawthorn (John Hawthorn) 26 Jun '26

26 Jun '26

Issue #21996 has been reported by jhawthorn (John Hawthorn). ---------------------------------------- Bug #21996: Crash when modifying instance variables during inspect or Marshal dump https://bugs.ruby-lang.org/issues/21996 * Author: jhawthorn (John Hawthorn) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- In #15968 describes an issue where instance variables being modified lead to incorrect Marshal output being generated, which was partially solved by checking for the number of IVs changing and raising an exception. However, if enough IVs removed this could cause the buffer to be moved/re-embedded, but we'd still attempt to read the now removed variables. I've found this reproduces back to Ruby 3.3, but suspect there are other ways to hit issues on older versions. We've seen the test from #15968 start failing on CI recently (likely because the changes to size pools makes this crash reproducible) https://github.com/ruby/ruby/actions/runs/24247666394/job/70803324392 ``` ruby class Evil def initialize(parent) @parent = parent end def marshal_dump @parent.instance_variables.each { |v| @parent.remove_instance_variable(v) } {} end def marshal_load(data) = nil end obj = Object.new obj.instance_variable_set(:@evil, Evil.new(obj)) 10.times { |i| obj.instance_variable_set(:"@v#{i}", 0) } Marshal.dump(obj) # SEGV ``` ``` ruby class Evil def initialize(parent) @parent = parent end def inspect @parent.instance_variables.each { |v| @parent.remove_instance_variable(v) } "" end end obj = Object.new obj.instance_variable_set(:@evil, Evil.new(obj)) 10.times { |i| obj.instance_variable_set(:"@v#{i}", 0) } obj.inspect # SEGV ``` -- https://bugs.ruby-lang.org/

3 2

[ruby-core:125841] [Ruby Bug#22131] Avoid array allocation in `Array#include?` on literal arrays
by Strech (Sergey Fedorov) 26 Jun '26

26 Jun '26

Issue #22131 has been reported by Strech (Sergey Fedorov). ---------------------------------------- Bug #22131: Avoid array allocation in `Array#include?` on literal arrays https://bugs.ruby-lang.org/issues/22131 * Author: Strech (Sergey Fedorov) * Status: Open * ruby -v: ruby 4.1.0dev * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- I've noticed that `Array#include?` on a literal array of frozen-shareable elements (Integers, Symbols, true/false/nil, frozen String literals) compiles the receiver to `duparray`, which allocates a fresh `Array` copy on every call — even though `#include?` only reads it. **Before** ```ruby # frozen_string_literal: true [1, 2].include?(3) ``` ``` == disasm: #<ISeq:<main>@-e:2 (2,0)-(2,18)> 0000 duparray [1, 2] ( 2)[Li] 0002 putobject 3 0004 opt_send_without_block <calldata!mid:include?, argc:1, ARGS_SIMPLE> 0006 leave ``` **After** ```ruby # frozen_string_literal: true [1, 2].include?(3) ``` ``` == disasm: #<ISeq:<main>@-e:2 (2,0)-(2,18)> 0000 putobject 3 ( 2)[Li] 0002 opt_duparray_send [1, 2], :include?, 1 0006 leave ``` **Benchmarks** ```ruby require 'benchmark/ips' GC.disable ARR = [1, 2, 3] Benchmark.ips do |x| x.report "literal [1,2,3].include?(2)" do |loop| loop.times { [1, 2, 3].include?(2) } end x.report "constant ARR.include?(2)" do |loop| loop.times { ARR.include?(2) } end x.compare! end ``` | case | master | candidate | speedup | |---|---|---|---:| | `[1,2,3].include?(2)` | 17.83M i/s (56.09 ns) | 30.00M i/s (33.33 ns) | 1.68x | | `ARR.include?(2)` (const) | 23.92M i/s (41.80 ns) | 23.92M i/s (41.81 ns) | ~1.00x | Github PR: https://github.com/ruby/ruby/pull/17496 -- https://bugs.ruby-lang.org/

2 3

[ruby-core:125762] [Ruby Bug#22115] [BUG] segmentation fault
by robert12 (Robert Gleeson) 26 Jun '26

26 Jun '26

Issue #22115 has been reported by robert12 (Robert Gleeson). ---------------------------------------- Bug #22115: [BUG] segmentation fault https://bugs.ruby-lang.org/issues/22115 * Author: robert12 (Robert Gleeson) * Status: Open * ruby -v: ruby 4.0.5 (2026-05-20 revision 64336ffd0e) +PRISM [x86_64-linux] * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- Hello. I did not reproduce this locally. I found it on CI. I'm reporting in case it has not been fixed or reported before. CI: https://github.com/llmrb/llm.rb/actions/runs/27511402478/job/81312014887 I hope this is helpful. I don't have more information except from the failed CI build. Thanks. ``` bundle exec rspec spec /home/runner/work/llm.rb/llm.rb/lib/llm/function/ractor/task.rb:69: warning: Ractor API is experimental and may change in future versions of Ruby. /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier.rb:74: [BUG] Segmentation fault at 0x000000000000002c ruby 4.0.5 (2026-05-20 revision 64336ffd0e) +PRISM [x86_64-linux] -- Control frame information ----------------------------------------------- c:0074 p:---- s:0402 e:000401 l:y b:---- CFUNC c:0073 p:0007 s:0399 e:000396 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier. c:0072 p:0008 s:0392 e:000391 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier. c:0071 p:0003 s:0388 e:000387 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier. c:0070 p:0024 s:0384 e:000383 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to. c:0069 p:0033 s:0378 e:000377 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to. c:0068 p:0018 s:0372 e:000371 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to. [FINISH] c:0067 p:---- s:0368 e:000367 l:y b:---- CFUNC :reject c:0066 p:0013 s:0364 e:000363 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to. c:0065 p:0007 s:0358 e:000357 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to. c:0064 p:0008 s:0353 e:000352 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/have_attrib c:0063 p:0013 s:0348 e:000347 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/have_attrib c:0062 p:0035 s:0343 e:000342 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/handler.rb:50 c:0061 p:0017 s:0338 e:000337 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/handler.rb:26 c:0060 p:0013 s:0331 e:000330 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/handler.rb:47 c:0059 p:0031 s:0323 e:000322 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/expectation_targ c:0058 p:0020 s:0316 e:000315 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/expectation_targ c:0057 p:0020 s:0309 e:000308 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/spec/openai/files_spec.rb:20 [FINISH] c:0056 p:---- s:0306 e:000305 l:y b:---- CFUNC :instance_exec c:0055 p:0021 s:0301 e:000300 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:263 c:0054 p:0002 s:0296 e:000295 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:511 c:0053 p:0002 s:0293 e:000292 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:468 c:0052 p:0002 s:0290 e:000289 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:486 c:0051 p:0002 s:0287 e:000286 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:626 c:0050 p:0018 s:0284 e:000283 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:352 c:0049 p:0004 s:0278 e:000277 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/webmock-3.24.0/lib/webmock/rspec.rb:39 [FINISH] c:0048 p:---- s:0274 e:000273 l:y b:---- CFUNC :instance_exec c:0047 p:0013 s:0269 e:000268 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:457 c:0046 p:0010 s:0263 e:000262 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:390 c:0045 p:0009 s:0257 e:000256 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:628 c:0044 p:0018 s:0254 e:000253 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:352 c:0043 p:0037 s:0248 E:000208 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:629 c:0042 p:0104 s:0241 E:0001c8 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:486 c:0041 p:0018 s:0234 E:0003f8 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:468 c:0040 p:0019 s:0229 E:001a38 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:511 c:0039 p:0076 s:0224 E:002698 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:259 c:0038 p:0047 s:0217 e:000216 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:653 [FINISH] c:0037 p:---- s:0211 e:000210 l:y b:---- CFUNC :map c:0036 p:0011 s:0207 e:000206 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:649 c:0035 p:0063 s:0202 e:000201 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:614 c:0034 p:0006 s:0193 e:000192 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:615 [FINISH] c:0033 p:---- s:0189 e:000188 l:y b:---- CFUNC :map c:0032 p:0076 s:0185 e:000184 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:615 c:0031 p:0007 s:0176 e:000175 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:121 [FINISH] c:0030 p:---- s:0172 e:000171 l:y b:---- CFUNC :map c:0029 p:0030 s:0168 e:000167 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:121 c:0028 p:0026 s:0165 e:000164 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:2097 c:0027 p:0006 s:0161 e:000160 l:n b:---- BLOCK /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:116 c:0026 p:0009 s:0157 e:000156 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/reporter.rb:74 c:0025 p:0019 s:0152 e:000151 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:115 c:0024 p:0035 s:0145 e:000144 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:89 c:0023 p:0080 s:0139 e:000138 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:71 c:0022 p:0013 s:0131 e:000130 l:y b:0001 METHOD /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:45 c:0021 p:0010 s:0126 e:000125 l:y b:0001 TOP /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/exe/rspec:4 [FINISH] c:0020 p:---- s:0123 e:000122 l:y b:---- CFUNC :load c:0019 p:0098 s:0118 e:000117 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/rubygems.rb:305 c:0018 p:0075 s:0109 e:000108 l:y b:0001 TOP /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/bin/rspec:25 [FINISH] c:0017 p:---- s:0104 e:000103 l:y b:---- CFUNC :load c:0016 p:0064 s:0099 e:000098 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli/exec.rb:61 c:0015 p:0063 s:0093 e:000092 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli/exec.rb:24 c:0014 p:0048 s:0088 e:000087 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli.rb:504 c:0013 p:0054 s:0082 e:000081 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor/command.rb:28 c:0012 p:0040 s:0074 e:000073 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor/invocation.rb:127 c:0011 p:0246 s:0067 e:000066 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor.rb:538 c:0010 p:0008 s:0054 e:000053 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli.rb:35 c:0009 p:0055 s:0049 e:000048 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor/base.rb:584 c:0008 p:0022 s:0042 e:000041 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli.rb:29 c:0007 p:0041 s:0037 e:000036 l:n b:---- BLOCK /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/gems/4.0.0/gems/bundler-4.0.10/exe/bundle:28 c:0006 p:0007 s:0031 e:000030 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/friendly_errors.rb:118 c:0005 p:0051 s:0026 E:0014a8 l:y b:0001 TOP /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/gems/4.0.0/gems/bundler-4.0.10/exe/bundle:20 [FINISH] c:0004 p:---- s:0022 e:000021 l:y b:---- CFUNC :load c:0003 p:0098 s:0017 e:000016 l:y b:0001 METHOD /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/rubygems.rb:305 c:0002 p:0079 s:0008 E:000be0 l:n b:---- EVAL /opt/hostedtoolcache/Ruby/4.0.5/x64/bin/bundle:25 [FINISH] c:0001 p:0000 s:0003 E:0004a0 l:y b:---- DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- /opt/hostedtoolcache/Ruby/4.0.5/x64/bin/bundle:25:in '<main>' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/rubygems.rb:305:in 'activate_and_load_bin_path' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/rubygems.rb:305:in 'load' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/gems/4.0.0/gems/bundler-4.0.10/exe/bundle:20:in '<top (required)>' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/friendly_errors.rb:118:in 'with_friendly_errors' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/gems/4.0.0/gems/bundler-4.0.10/exe/bundle:28:in 'block in <top (required)>' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli.rb:29:in 'start' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor/base.rb:584:in 'start' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli.rb:35:in 'dispatch' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor.rb:538:in 'dispatch' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in 'invoke_command' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/vendor/thor/lib/thor/command.rb:28:in 'run' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli.rb:504:in 'exec' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli/exec.rb:24:in 'run' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli/exec.rb:61:in 'kernel_load' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/bundler/cli/exec.rb:61:in 'load' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/bin/rspec:25:in '<top (required)>' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/rubygems.rb:305:in 'activate_and_load_bin_path' /opt/hostedtoolcache/Ruby/4.0.5/x64/lib/ruby/4.0.0/rubygems.rb:305:in 'load' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/exe/rspec:4:in '<top (required)>' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:45:in 'invoke' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:71:in 'run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:89:in 'run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:115:in 'run_specs' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/reporter.rb:74:in 'report' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:116:in 'block in run_specs' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:2097:in 'with_suite_hooks' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:121:in 'block (2 levels) in run_specs' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:121:in 'map' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:121:in 'block (3 levels) in run_specs' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:615:in 'run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:615:in 'map' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:615:in 'block in run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:614:in 'run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:649:in 'run_examples' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:649:in 'map' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:653:in 'block in run_examples' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:259:in 'run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:511:in 'with_around_and_singleton_context_hooks' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:468:in 'with_around_example_hooks' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:486:in 'run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:629:in 'run_around_example_hooks_for' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:352:in 'call' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:628:in 'block (2 levels) in run_around_example_hooks_for' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:390:in 'execute_with' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:457:in 'instance_exec' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:457:in 'instance_exec' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/webmock-3.24.0/lib/webmock/rspec.rb:39:in 'block (2 levels) in <top (required)>' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:352:in 'call' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:626:in 'block in run_around_example_hooks_for' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/hooks.rb:486:in 'block in run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:468:in 'block in with_around_example_hooks' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:511:in 'block in with_around_and_singleton_context_hooks' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:263:in 'block in run' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example.rb:263:in 'instance_exec' /home/runner/work/llm.rb/llm.rb/spec/openai/files_spec.rb:20:in 'block (3 levels) in <top (required)>' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/expectation_target.rb:101:in 'to' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/expectation_target.rb:65:in 'to' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/handler.rb:47:in 'handle_matcher' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/handler.rb:26:in 'with_matcher' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/expectations/handler.rb:50:in 'block in handle_matcher' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/have_attributes.rb:28:in 'matches?' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/have_attributes.rb:90:in 'respond_to_attributes?' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to.rb:78:in 'matches?' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to.rb:114:in 'find_failing_method_names' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to.rb:114:in 'reject' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to.rb:115:in 'block in find_failing_method_names' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to.rb:120:in 'matches_arity?' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-expectations-3.13.5/lib/rspec/matchers/built_in/respond_to.rb:180:in 'matches?' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier.rb:344:in 'valid?' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier.rb:375:in 'missing_kw_args' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rspec-support-3.13.7/lib/rspec/support/method_signature_verifier.rb:74:in 'missing_kw_args_from' rake aborted! Command failed with status (): [bundle exec rspec spec] /home/runner/work/llm.rb/llm.rb/Rakefile:41:in 'block in <top (required)>' /home/runner/work/llm.rb/llm.rb/vendor/bundle/ruby/4.0.0/gems/rake-13.4.2/exe/rake:27:in '<top (required)>' /opt/hostedtoolcache/Ruby/4.0.5/x64/bin/bundle:25:in '<main>' Tasks: TOP => default => spec (See full trace by running task with --trace) ................................................ ``` -- https://bugs.ruby-lang.org/

2 3

[ruby-core:125833] [Ruby Bug#22129] error_highlight raises NotImplementedError for ArgumentErrors that get wrapped
by rwstauner (Randy Stauner) 25 Jun '26

25 Jun '26

Issue #22129 has been reported by rwstauner (Randy Stauner). ---------------------------------------- Bug #22129: error_highlight raises NotImplementedError for ArgumentErrors that get wrapped https://bugs.ruby-lang.org/issues/22129 * Author: rwstauner (Randy Stauner) * Status: Open * Backport: 3.3: DONTNEED, 3.4: DONTNEED, 4.0: REQUIRED ---------------------------------------- With code like ```ruby def x(y:) = y begin x rescue => e p e.exception("wat").detailed_message end ``` a NotImplementedError is raised on ruby 4.0+ ```/Users/rwstauner/.rubies/4.0.2/lib/ruby/4.0.0/error_highlight/base.rb:297:in 'ErrorHighlight::Spotter#spot': NotImplementedError (NotImplementedError) from /Users/rwstauner/.rubies/4.0.2/lib/ruby/4.0.0/error_highlight/base.rb:68:in 'ErrorHighlight.spot' from /Users/rwstauner/.rubies/4.0.2/lib/ruby/4.0.0/error_highlight/core_ext.rb:34:in 'ErrorHighlight::CoreExt#generate_snippet' from /Users/rwstauner/.rubies/4.0.2/lib/ruby/4.0.0/error_highlight/core_ext.rb:43:in 'ErrorHighlight::CoreExt#detailed_message' from tiny.rb:6:in 'Exception#full_message' from tiny.rb:6:in '<main>' tiny.rb:1:in 'Object#x': missing keyword: :y (ArgumentError) caller: tiny.rb:4 | x ^ callee: tiny.rb:1 | def x(y:) = y ^ from tiny.rb:4:in '<main>' ``` on ruby 3.4 it did not raise: ``` tiny.rb:1:in 'x': wat (ArgumentError) from tiny.rb:4:in '<main>' ``` seems related to https://bugs.ruby-lang.org/issues/21543 I have a PR up at https://github.com/ruby/error_highlight/pull/78 -- https://bugs.ruby-lang.org/

2 2

[ruby-core:116949] [Ruby master Misc#20303] Troubleshooting Guide for Common Issues with GMC Acadia
by adamrojas (Adam Rojas) 23 Jun '26

23 Jun '26

Issue #20303 has been reported by adamrojas (Adam Rojas). ---------------------------------------- Misc #20303: Troubleshooting Guide for Common Issues with GMC Acadia https://bugs.ruby-lang.org/issues/20303 * Author: adamrojas (Adam Rojas) * Status: Open ---------------------------------------- Owning a GMC Acadia brings numerous benefits, yet like any vehicle, it may encounter issues. In this guide, we’ll delve into common problems reported by GMC Acadia owners and offer effective solutions. ![Troubleshooting Guide for Common Issues with GMC Acadia](https://autorepairandservice.files.wordpress.com/2024/02/troublesho… Whether you’re dealing with transmission faults, engine light codes, or other issues, we’ve got you covered. ## **Troubles with Transmission and Check Engine Light:** ![Troubles with Transmission and Check Engine Light](https://autorepairandservice.files.wordpress.com/2024/02/troubles-wi… One significant challenge faced by GMC Acadia owners revolves around transmission faults, often accompanied by the illumination of the check engine light. This issue, reported by numerous individuals, demands prompt attention to prevent further complications. Seeking assistance from experienced professionals is recommended to diagnose and address these transmission-related concerns effectively, ensuring the continued reliability and performance of your vehicle. ## **Interpreting Check Engine Light Codes:** ![Interpreting Check Engine Light Codes](https://autorepairandservice.files.wordpress.com/2024/02/interpretin… Another common issue encountered by GMC Acadia owners involves the activation of the check engine light, often accompanied by specific diagnostic trouble codes (DTCs). Understanding these codes is essential for identifying underlying issues promptly. Seeking assistance from a qualified mechanic for thorough diagnostics and appropriate remedies is advised to prevent potential engine damage and ensure continued vehicle reliability. ## **Addressing Gas Cap Concerns and Check Engine Light Illumination:** ![Addressing Gas Cap Concerns and Check Engine Light Illumination](https://autorepairandservice.files.wordpress.com/2024/02/addr… Another area of concern for GMC Acadia owners involves issues related to the gas cap, which can lead to the illumination of the check engine light. This problem, while less common, should not be overlooked. It’s important to ensure the gas cap is securely tightened to prevent evaporation and maintain proper fuel system pressure. If the check engine light persists after verifying the gas cap’s tightness, seeking assistance from a qualified technician is advisable to diagnose and resolve any underlying issues effectively. ## **Navigating GMC Acadia Electrical Issues:** ![Navigating GMC Acadia Electrical Issues](https://autorepairandservice.files.wordpress.com/2024/02/navigating… Electrical problems can pose significant challenges for GMC Acadia owners, affecting various systems within the vehicle. These issues might manifest as malfunctioning lights, power window failures, intermittent electrical failures, or battery drainage concerns. Addressing electrical problems promptly is crucial to prevent further complications and ensure the safety and functionality of your Acadia. Seeking assistance from experienced technicians equipped with diagnostic tools and expertise in automotive electrical systems is essential for accurately identifying and resolving these issues, restoring your vehicle’s performance and reliability. ## **Essential Maintenance Tasks for GMC Acadia Owners:** ![Essential Maintenance Tasks for GMC Acadia Owners](https://autorepairandservice.files.wordpress.com/2024/02/essential-… Beyond adhering to scheduled maintenance, there are fundamental tasks that every GMC Acadia owner should prioritize. These include: **1. Regular Brake Fluid Flushes:** To uphold braking effectiveness, it’s crucial to schedule regular brake fluid flushes. This process helps prevent contaminants from compromising the brake system’s performance, ensuring optimal safety on the road. **2. Transmission Inspections:** Regular inspections of the transmission are essential for early detection of potential issues. By identifying any signs of wear or malfunction early on, owners can mitigate the risk of costly repairs and ensure smooth operation of their Acadia. **3. Coolant Inspections:** Preventing overheating is vital for maintaining engine health. Regular coolant inspections help owners monitor coolant levels and quality, ensuring proper engine temperature regulation and preventing potential damage due to overheating. **4. Spark Plug Replacements:** Spark plugs play a critical role in engine performance by igniting the air-fuel mixture in the cylinders. Replacing worn-out spark plugs at recommended intervals helps maintain fuel efficiency, prevent misfires, and ensure optimal engine performance. ## **Expert Tips for GMC Acadia Owners:** ![Expert Tips for GMC Acadia Owners](https://autorepairandservice.files.wordpress.com/2024/02/expert-tip… Routine inspections and preventive measures are key to maintaining your GMC Acadia’s performance and longevity. Beyond addressing specific issues and adhering to maintenance schedules, here are some expert tips to keep your vehicle running smoothly: **1. Driving Habits Matter:** Be mindful of your driving habits to minimize wear and tear on your Acadia. Avoid sudden acceleration or braking whenever possible, and practice smooth, gradual maneuvers to reduce strain on the engine, transmission, and other vital components. **2. Stay Informed and Educated:** Stay updated on recalls, service bulletins, and manufacturer recommendations for your GMC Acadia. Joining online forums or communities dedicated to GMC owners can provide valuable insights and tips from fellow enthusiasts and experts. Keeping yourself informed empowers you to make informed decisions about your vehicle’s care and maintenance. By incorporating these expert tips into your maintenance routine, you can ensure that your GMC Acadia remains reliable, efficient, and enjoyable to drive for miles to come. ## **Conclusion:** Being aware of common GMC Acadia issues and following proper maintenance practices can ensure trouble-free ownership. Promptly addressing problems through professional diagnosis and repair, along with adhering to recommended maintenance intervals, can help maintain a reliable and enjoyable driving experience. Thank you for reading this post. If you're looking for a car specialist to opt for a [cheap plastic bumper repair in Manchester](https://servicemycar.com/uk/services/car-bumper-repair-manchest…. So, you can connect with Service My Car and get the best car dent service at a very reasonable price. -- https://bugs.ruby-lang.org/

2 2