346d1f63b7 only added the assertion. To find where the terminator length of 6 comes from, I added the same check to `STR_EMBEDDABLE_P` by hand and built the two commits around 14285dee21 ("Optimize `String.new(capacity:)`", https://githu...yahonda (Yasuo Honda)
The Rails nightly CI against Ruby master (debug build) started aborting in Active Support with `Assertion Failed: STR_EMBEDDABLE_P:termlen <= 4: too big termlen: 6`. It bisects to 346d1f63b7 ("Ignore negative capacity", https://github.co...yahonda (Yasuo Honda)
Let me report a recent change in behaviour that is related to this ticket. I noticed it while investigating https://github.com/bcrypt-ruby/bcrypt-ruby/issues/305 , which appeared after the `rubylang/ruby` Docker images moved to Ubuntu 26...yahonda (Yasuo Honda)
The Rails nightly CI against Ruby master started crashing with `[BUG] rb_objspace_reachable_objects_from_local: set is owned by another Ractor` in Action Pack and Action View on all of master, YJIT and master-debug. It bisects to f0439cd...yahonda (Yasuo Honda)
This issue is originally found at the Rails nightly CI with a debug build of Ruby. It started failing at https://buildkite.com/rails/rails-nightly/builds/4738#01a0ac05-212c-406d-bec7-190726eecc98 with ruby 4.1.0dev (2026-09-16T14:21:47Z ...yahonda (Yasuo Honda)
This assertion failure does not reproduce since https://github.com/ruby/ruby/commit/09aab7899fa0d0014e458c319e689175881a2075 so I think we can close it.yahonda (Yasuo Honda)
On ruby-head, the Active Support (Rails) test suite fails with two Ractor-related errors (rails-nightly build 4651, https://buildkite.com/rails/rails-nightly/builds/4651#01a016ac-eada-492d-9548-44089079b973/L8324). Rails CI failure. T...yahonda (Yasuo Honda)
Correction on the bisect result. 98f0921f2b is where the forked RailtieTest children start to crash (SIGSEGV or ArgumentError), not where this NoMethodError starts. Bisecting for the NoMethodError itself, with the same bin/test command, ...yahonda (Yasuo Honda)