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

[ruby-core:120891] [Ruby master Feature#21116] Extract RJIT as a third-party gem
by k0kubun (Takashi Kokubun) 06 Feb '25

06 Feb '25

Issue #21116 has been reported by k0kubun (Takashi Kokubun). ---------------------------------------- Feature #21116: Extract RJIT as a third-party gem https://bugs.ruby-lang.org/issues/21116 * Author: k0kubun (Takashi Kokubun) * Status: Open ---------------------------------------- ## Proposal * Extract the implementation of `RJIT::C` to ruby/rjit and publish it as a thirt-party gem * Allow `jit_exec()` to call `body->jit_entry` even when `--yjit` is not given * Remove RJIT from the Ruby core ## Background * RJIT depends on `fiddle`, and `fiddle` is extracted as a bundled gem. @hsbt and @nobu are struggling to maintain the dependency from the Ruby core to a bundled gem. * Integrating RJIT into the Ruby core has forced VM maintainers to update RJIT with every VM change, significantly increasing the maintenance burden. * I thought you couldn't implement `RJIT::C` as a third-party gem when I introduced RJIT [Feature #19420]. However, now @tenderlovemaking and I think it's possible if we modify `jit_exec()` as explained in the proposal. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116983] [Ruby master Feature#20309] Bundled gems for Ruby 3.5
by hsbt (Hiroshi SHIBATA) 06 Feb '25

06 Feb '25

Issue #20309 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Feature #20309: Bundled gems for Ruby 3.5 https://bugs.ruby-lang.org/issues/20309 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- I propose migrate the following default gems to bundled gems at Ruby 3.5. So, It means users will get warnings if users try to load them. * ostruct * irb * reline * readline (wrapper file for readline-ext and reline) * io-console * logger * fiddle * pstore * open-uri * yaml (wrapper file for psych) * win32ole I have a plan to migrate the following default gems too. But I need to more feedback from other committers about them. * rdoc * We need to change build task like download rdoc gem before document generation. * or We make document generation is optional from Ruby 3.5 * We explicitly separate `make install` and `make install-doc` * un * `ruby -run` is one of cool feature of Ruby. Should we avoid uninstalling `un` gem? * singleton * This is famous design pattern. Should we enforce users add them to their Gemfile? * forwadable * `reline` needs to add forwardable their `runtime_dependency` after migration. * weakref * I'm not sure how impact after migrating bundled gems. * fcntl * Should we integrate these constants into ruby core? I would like to migrate `ipaddr` and `uri` too. But these are used by webrick that is mock server for our test suite. We need to rewrite `webrick` with `TCPSocker` or extract `ipaddr` and `uri` dependency from `webrick` Other default gems depend on our build process or other libraries deeply. I will update this proposal if I could extract them from default gems. -- https://bugs.ruby-lang.org/

9 27

[ruby-core:120643] [Ruby master Feature#21033] Allow lambdas that don't access `self` to be Ractor shareable
by tenderlovemaking (Aaron Patterson) 04 Feb '25

04 Feb '25

Issue #21033 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Feature #21033: Allow lambdas that don't access `self` to be Ractor shareable https://bugs.ruby-lang.org/issues/21033 * Author: tenderlovemaking (Aaron Patterson) * Status: Open ---------------------------------------- Hi, I would like to allow lambdas that don't access `self` to be eligible for Ractor shareability regardless of the shareability status of `self`. Consider the following code: ```ruby class Foo def make_lambda x = 123 lambda { x } end end Ractor.make_shareable(Foo.new.make_lambda) ``` With Ruby 3.4.X, this will raise an exception. The reason is because `self`, which is an unfrozen instance of `Foo`, is not shareable. However, we can see from the code that the lambda doesn't access `self`. I would like to make lambdas such as the ones above eligible for shareability, and I've submitted a patch [here](https://github.com/ruby/ruby/pull/12567). I think we can detect access to `self` by scanning the instructions in the lambda. Any references to `putself`, `getinstancevariable`, or `setinstancevariable` will result in using the default behavior (checking the frozen status of `self`). ## Considerations ### What about `eval`? I think that `eval` is not a problem because calling eval has an implicit reference to `self`: ``` $ ./miniruby --dump=insns -e 'lambda { eval("123") }' == disasm: #<ISeq:<main>@-e:1 (1,0)-(1,22)> 0000 putself ( 1)[Li] 0001 send <calldata!mid:lambda, argc:0, FCALL>, block in <main> 0004 leave == disasm: #<ISeq:block in <main>@-e:1 (1,7)-(1,22)> 0000 putself ( 1)[LiBc] 0001 putchilledstring "123" 0003 opt_send_without_block <calldata!mid:eval, argc:1, FCALL|ARGS_SIMPLE> 0005 leave [Br] ``` If we try to call `eval` inside the lambda, there will be an implicit `putself` instruction added which means we will fall back to the old behavior. ### What about `binding`? If you call `binding` from inside the `lambda` there will be a `putself` instruction so we fall back to the old behavior. This is the same as the `eval` case. ### What about `binding` via a local? If you assign `binding` to a local, shareability will fail because the `lambda` references an unshareable local: ```ruby class Foo def make_lambda x = binding lambda { x } end end b = Foo.new.make_lambda # exception because local `x` is not shareable Ractor.make_shareable(b) ``` ### What about accessing `binding` via the proc itself? The lambda can references itself via a local and access binding, but again this will fail isolation when locals are scanned: ```ruby class Foo def make_lambda x = lambda { x.binding.eval("self") } end end b = Foo.new.make_lambda # exception because local `x` is not shareable Ractor.make_shareable(b) ``` I _think_ I've covered all cases where `self` can possibly escape. I would appreciate any feedback. Again, [here is the patch](https://github.com/ruby/ruby/pull/12567). Thanks. -- https://bugs.ruby-lang.org/

4 17

[ruby-core:120795] [Ruby master Bug#21090] SEGV from require in Thread in Ractor
by wanabe (_ wanabe) 02 Feb '25

02 Feb '25

Issue #21090 has been reported by wanabe (_ wanabe). ---------------------------------------- Bug #21090: SEGV from require in Thread in Ractor https://bugs.ruby-lang.org/issues/21090 * Author: wanabe (_ wanabe) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-18T00:19:17Z origin/master 65a7c69188) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- When ruby calls 'require' in Thread in non-main Ractor, it can cause SEGV sometimes. ``` $ ruby -e '1000.times { Ractor.new { th = Thread.new { require "rbconfig" }; Thread.pass }.take }' > segv.log 2>&1 Segmentation fault (core dumped) ``` `segv.log` is too large to paste in this description, so I attached as a file. ---Files-------------------------------- segv.log (36.9 KB) -- https://bugs.ruby-lang.org/

2 2

[ruby-core:120774] [Ruby master Bug#21087] "try to mark T_NONE object" error in ActiveRecord with 3.4.1 upgrade
by p8 (Petrik de Heus) 02 Feb '25

02 Feb '25

Issue #21087 has been reported by p8 (Petrik de Heus). ---------------------------------------- Bug #21087: "try to mark T_NONE object" error in ActiveRecord with 3.4.1 upgrade https://bugs.ruby-lang.org/issues/21087 * Author: p8 (Petrik de Heus) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The TechEmpower benchmarks for `rage` fail when setting the `isolation_level` to `:fiber`. The bug can be replicated by checking out [the branch](https://github.com/p8/FrameworkBenchmarks/tree/rage/fiber) and running the following: ```bash ./tfb --test rage --type fortune ``` The error: ``` rage: rb_obj_info_dump: �s�� rage: /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/explain_registry.rb:34: [BUG] try to mark T_NONE object rage: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT +PRISM [aarch64-linux] rage: -- Control frame information ----------------------------------------------- rage: c:0040 p:0007 s:0276 e:000275 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/explain_registry.rb:34 rage: c:0039 p:0003 s:0272 e:000271 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/explain_registry.rb:25 [FINISH] rage: c:0038 p:---- s:0268 e:000267 CFUNC :new rage: c:0037 p:0016 s:0264 e:000260 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/explain_registry.rb:17 rage: c:0036 p:0003 s:0257 e:000256 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/explain_registry.rb:13 rage: c:0035 p:0004 s:0250 e:000249 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/explain_subscriber.rb:13 rage: c:0034 p:0010 s:0243 e:000242 BLOCK /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:162 rage: c:0033 p:0005 s:0239 e:000238 BLOCK /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:25 rage: c:0032 p:0027 s:0234 e:000233 METHOD <internal:array>:228 rage: c:0031 p:0008 s:0228 e:000227 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:24 rage: c:0030 p:0010 s:0222 e:000221 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:122 rage: c:0029 p:0004 s:0217 e:000216 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:161 rage: c:0028 p:0010 s:0210 e:000209 BLOCK /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:259 rage: c:0027 p:0005 s:0206 e:000205 BLOCK /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:25 rage: c:0026 p:0027 s:0201 e:000200 METHOD <internal:array>:228 rage: c:0025 p:0008 s:0195 e:000194 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:24 rage: c:0024 p:0018 s:0189 e:000188 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:258 rage: c:0023 p:0012 s:0182 e:000181 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/fanout.rb:251 rage: c:0022 p:0035 s:0178 e:000176 METHOD /usr/local/bundle/gems/activesupport-7.2.2.1/lib/active_support/notifications/instrumenter.rb:64 [FINISH] rage: c:0021 p:0047 s:0169 e:000168 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract_adapter.rb:1119 [FINISH] rage: c:0020 p:0031 s:0156 e:000155 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:892 rage: c:0019 p:0041 s:0144 e:000143 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:872 rage: c:0018 p:0026 s:0130 e:000129 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:66 rage: c:0017 p:0093 s:0118 e:000117 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract/database_statements.rb:647 rage: c:0016 p:0064 s:0105 e:000104 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract/database_statements.rb:73 [FINISH] rage: c:0015 p:0143 s:0093 e:000092 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract/query_cache.rb:251 [FINISH] rage: c:0014 p:0025 s:0080 e:000079 BLOCK /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/relation/calculations.rb:318 rage: c:0013 p:0030 s:0076 e:000075 METHOD /usr/local/bundle/gems/rage-rb-1.11.0/lib/rage/ext/active_record/connection_pool.rb:205 [FINISH] rage: c:0012 p:0011 s:0069 e:000068 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/connection_handling.rb:296 rage: c:0011 p:0022 s:0062 e:000061 BLOCK /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/relation/calculations.rb:317 rage: c:0010 p:0015 s:0059 e:000058 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/relation.rb:1452 rage: c:0009 p:0120 s:0054 e:000053 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/relation/calculations.rb:313 [FINISH] rage: c:0008 p:0012 s:0046 e:000045 METHOD /usr/local/bundle/gems/activerecord-7.2.2.1/lib/active_record/querying.rb:24 rage: c:0007 p:0008 s:0037 e:000036 METHOD /rage/app/controllers/benchmarks_controller.rb:32 rage: c:0006 p:0038 s:0032 e:000031 METHOD /usr/local/bundle/gems/rage-rb-1.11.0/lib/rage/controller/api.rb:98 rage: c:0005 p:0010 s:0028 e:000027 BLOCK (eval at /usr/local/bundle/gems/rage-rb-1.11.0/lib/rage/router/backend.rb:79):1 [FINISH] rage: c:0004 p:0043 s:0023 e:000019 METHOD /usr/local/bundle/gems/rage-rb-1.11.0/lib/rage/application.rb:16 rage: c:0003 p:0008 s:0011 e:000010 BLOCK /usr/local/bundle/gems/rage-rb-1.11.0/lib/rage/middleware/fiber_wrapper.rb:19 [FINISH] rage: c:0002 p:0016 s:0008 e:000005 BLOCK /usr/local/bundle/gems/rage-rb-1.11.0/lib/rage/fiber_scheduler.rb:122 [FINISH] rage: c:0001 p:---- s:0003 e:000002 DUMMY [FINISH] rage: -- Ruby level backtrace information --------------------------------------- ``` -- https://bugs.ruby-lang.org/

3 5

[ruby-core:120862] [Ruby master Feature#21109] Want to clarify how $/ is handled in Ractor
by wanabe (_ wanabe) 02 Feb '25

02 Feb '25

Issue #21109 has been reported by wanabe (_ wanabe). ---------------------------------------- Feature #21109: Want to clarify how $/ is handled in Ractor https://bugs.ruby-lang.org/issues/21109 * Author: wanabe (_ wanabe) * Status: Open ---------------------------------------- I am often in trouble because `$/` is inaccessible in Ractor. For example, `IO#readline` can't be called from non-main Ractor. ``` $ echo "foo"|ruby -e 'Ractor.new do p $stdin.readline end.take' -e:1: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues. #<Thread:0x00007efbf5ab4f58 run> terminated with exception (report_on_exception is true): <internal:io>:133:in 'IO#readline': can not access global variables $/ from non-main Ractors (Ractor::IsolationError) from -e:1:in 'block in <main>' <internal:ractor>:711:in 'Ractor#take': thrown by remote Ractor. (Ractor::RemoteError) from -e:1:in '<main>' <internal:io>:133:in 'IO#readline': can not access global variables $/ from non-main Ractors (Ractor::IsolationError) from -e:1:in 'block in <main>' ``` But when I use `Kernel.#readline` in Ractor, the behavior is as same as main Ractor. This behavior changes depending on whether accessing the global variable `$/` in ruby or the internal `rb_rs` in C. ``` $ echo "foo"|ruby -e '$/ = "o"; Ractor.new do p readline end.take' -e:1: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues. "fo" ``` I think it would be better if the behavior is unified and easy to understand. It would be ideal if it is possible to read and write from Ractor, but even if not, it would be nice if it is at least unified to reduce confusion. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:120858] [Ruby master Feature#21107] Add a Ractor safety & shareability section to stdlib class docs
by osyoyu (Daisuke Aritomo) 02 Feb '25

02 Feb '25

Issue #21107 has been reported by osyoyu (Daisuke Aritomo). ---------------------------------------- Feature #21107: Add a Ractor safety & shareability section to stdlib class docs https://bugs.ruby-lang.org/issues/21107 * Author: osyoyu (Daisuke Aritomo) * Status: Open ---------------------------------------- ## Proposal Add a section describing Ractor safety and shareability for each stdlib class. For example, a description for Array could look like: ``` == Ractor safety and shareability An \Array is not Ractor shareable by default. It can be turned shareable if the following conditions are met: - The \Array itself is frozen. - All elements in the \Array are Ractor shareable as well. ``` Or, for Random: ``` == Ractor safety shareability A \Random instance cannot be made Ractor shareable. This is because of its nature having a internal state. However, Random.srand and Random.rand can be called inside Ractors. Use those if you just need a random number inside a Ractor. ``` ## Background Currently, it is not so easy to know if a object is Ractor shareable or not. While `Ractor.shareable?` exists, it is painful to test each object during programming. It does not provide information on why a object is not Ractor shareable, how it can be Ractor shareable, or if that is possible in the first place. Having this kind of information would be very helpful when writing Ractor code. It will help programmers choose more Ractor-friendly data structures and system designs. Including why the class is not Ractor-shareable could also promote efforts making the Ruby ecosystem more Ractor-compatible. ## Appendix: The SAFETY section in Rust docs The Rust language docs has a similar concept. All functions that are marked as `unsafe` are expected to have a `SAFETY` section in their documentation. The section should state why the function is unsafe, what preconditions shall be met before calling, and what can happen if those are not fulfilled. https://std-dev-guide.rust-lang.org/policy/safety-comments.html For example, documentation for std::vec::Vec.set_len states what preconditions the implementation expects, and provides examples for other safe ways. ``` Forces the length of the vector to new_len. This is a low-level operation that maintains none of the normal invariants of the type. Normally changing the length of a vector is done using one of the safe operations instead, such as truncate, resize, extend, or clear. Safety - new_len must be less than or equal to capacity(). - The elements at old_len..new_len must be initialized. ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:120857] [Ruby master Bug#21106] The last iteration of the rb_ary_shuffle_bang function is useless
by usumerican (usumerican _) 02 Feb '25

02 Feb '25

Issue #21106 has been reported by usumerican (usumerican _). ---------------------------------------- Bug #21106: The last iteration of the rb_ary_shuffle_bang function is useless https://bugs.ruby-lang.org/issues/21106 * Author: usumerican (usumerican _) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-darwin21] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The number of iterations in the Fischer-Yates shuffle is (N-1) times. In the following verification code, rand function is called N times. ``` class R def rand(n) puts n return 0 end end a = [1,2,3,4,5,6,7,8,9,10] puts a.shuffle(random: R.new).join(",") ``` The while conditional expression in the rb_ary_shuffle_bang function can be changed from while(n) to while(n > 1). https://github.com/ruby/ruby/blob/db02a6b3ab4cabbdf492c26dcb1929b4ef0370a1/… -- https://bugs.ruby-lang.org/

1 0