Activity
From 12/18/2025 to 12/24/2025
Today
-
10:44 AM Revision c17307ac (git): Rollback to test-unit 3.7.3
- 3.7.5 is not working with rbs-3.10.0
https://github.com/ruby/ruby/actions/runs/20480628393/job/58853288287#step:22:353
```
D:/a/ruby/ruby/src/.bundle/gems/test-unit-3.7.5/lib/test/unit/testcase.rb:641:in 'block (2 levels) in Test::Un... -
-
-
-
-
- 06:55 AM Revision 04a64622 (git): Update bundled gems list as of 2025-12-24
-
06:43 AM Revision 88d6c5aa (git): [DOC] Update ZJIT status in NEWS.md
- As for Ruby v4.0.0-preview3, ZJIT support is enabled by default on
supported platforms. The previous phrasing is not relevant for most
users. Replaced with brief instructions for enabling the JIT itself. - 06:10 AM Revision f7b48456 (git): Box: show the fully qualified URL of the Ruby::Box doc
-
05:41 AM Revision 352de161 (git): Remove an extra dot from `RUBY_API_VERSION_STR`
-
05:10 AM Revision fc19ce0a (git): Lrama v0.7.1
-
- Fix GH-15061
-
-
-
03:30 AM Revision 342d2578 (git): [DOC] Fix backticks in Coverage.peek_result
-
-
02:46 AM Revision ab683d56 (git): [DOC] Cross-links between Japanese and English pages (#15705)
- * [DOC] Cross-links between Japanese and English pages
-
02:21 AM Revision 9154d72a (git): Improve CGI.escape* docs
-
02:14 AM Revision 10a68210 (git): [DOC] Fix IO::Buffer document
- 02:03 AM Revision 6e2bf5df (git): [Tests] Assert Module#set_temporary_name returns self
- The return value of Module#set_temporary_name was changed
to return `self`, but the existing tests
did not verify this. -
01:59 AM Revision ceea8060 (git): Properly handle test cases terminated by signals in test-bundled-gems
- Process::Status#exitstatus turn into nil when child process is signeled.
When exit_code was unchanged, test-bundled-gems.rb returned 0 and make was unable to detect the failure. Fix this. -
- In ruby, since 3.1 at least, the words "Pattern Matching" should refer
the syntax. - 01:39 AM Revision e2a58c45 (git): [DOC] Fix minor typo in signals.rdoc
- 01:10 AM Revision 30d9782c (git): Tidy up fiber scheduler tests.
- 01:10 AM Revision 2df72c0c (git): Fix flaky test.
-
12/23/2025
-
-
- * Describe base code layout rules
* Enhance optional keyword explanation
* Change the logical operators description -
- RDoc does not parse the documentation for the Method#call aliases, so we
should combine the aliases into one documentation. -
12:59 PM Bug #21802: segmentation fault when installing gems on CI
- ufuk (Ufuk Kayserilioglu) wrote in #note-2:
> Please post the C level backtrace as well. Usually that's very helpful.
any idea how I could do that? the job inside the CI most of the time simply dies with an output like this:
```
/b... -
12:52 PM Bug #21802: segmentation fault when installing gems on CI
- Please post the C level backtrace as well. Usually that's very helpful.
-
- hey!
recently, we updated to Bundler v4 (currently running v4.0.3) and Ruby 3.4.8. Since then, one of our CircleCI steps has been failing repeatedly, often without logs. Sometimes it does fail with a log
```
Installing faraday-typ... - 12:51 PM Revision ab565a3e (git): Box: split the test for CI timeouts
-
12:43 PM Bug #21801: compile failed at 4.0.0 preview 3 and snapshot issue
- darkspy (gerty ken) wrote in #note-3:
> nobu (Nobuyoshi Nakada) wrote in #note-2:
> ...
now snapshot tonight:
compiling ./missing/langinfo.c
compiling ./missing/crypt.c
compiling ./missing/explicit_bzero.c
compiling ./missing/ffs.c... -
- `Dir.mktmpdir` concatenates a random base-36 number separated by "-",
so may generate pathnames containing "-j4". - 08:52 AM Revision 3ddf6950 (git): Update bundled gems list as of 2025-12-23
-
08:51 AM Revision 2ed9a7bd (git): Bundle RBS 3.10.0 (#15701)
- * Bundle RBS 3.10.0
* Unskip BigDecimal tests -
- I have no enough time to handle this for Ruby 4.0.0.
Please add `irb` to your Gemfile or wait to release 4.0.1. Sorry to your inconvenience. -
08:28 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- So first, I must say I agree this is a common problem with the advent of containers. Both Rails and Puma tried to have automatic detection and configuration of the number of worker processes, and it caused issue for users on various plat...
-
- Yes. `Foo` is a constant, not a method. The example was wrong. Now that it's updated we can close.
-
08:02 AM Revision d879f9f6 (git): [DOC] Fix example in Ruby::Box documentation
-
- 07:11 AM Revision 3a92e07a (git): Update default gems list at 1c3ef2719155b56f14bf734c82b26e [ci skip]
-
- 04:04 AM Revision ed1aac54 (git): Update default gems list at 8eaf6739fda591233b07f3ada7ed4e [ci skip]
-
04:03 AM Revision 8eaf6739 (git): [ruby/error_highlight] Bump version
- https://github.com/ruby/error_highlight/commit/dc2dad6632
-
02:31 AM Feature #21796: unpack variant that returns the final offset
- I like `^` specifier too.
Matz.
-
12/22/2025
-
- nobu (Nobuyoshi Nakada) wrote in #note-2:
> darkspy (gerty ken) wrote:
> ...
yep like for 8 years compiling ruby using msys 1.0 + winlib / mingw64. until 4.0 preview2 were fine -
- darkspy (gerty ken) wrote:
> ENV:
> ...
Are you really using msys **1.0**? -
- ```
compiling x64-msvcrt-ruby400.res.o
creating verconf.h
verconf.h updated
compiling loadpath.c
linking static-library libx64-msvcrt-ruby400-static.a
generating x64-msvcrt-ruby400.def
linking shared-library x64-msvcrt-ruby400.dll... -
- * [DOC] Languages in Examples
* Update doc/contributing/documentation_guide.md
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
* Update doc/contributing/documentation_guide.md
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
... -
- This heap emulates the growth characteristics of the Ruby default GC's
heap. By default, the heap grows by 40%, requires at least 20% empty
after a GC, and allows at most 65% empty before it shrinks the heap. This
is all configurable via... - 06:22 PM Revision 481f16f3 (git): [DOC] Improve ractor class docs (grammar, code examples) (#15686)
-
-
-
12:00 PM Revision 5272f2bc (git): Bump RDoc to 7.0.2 (#15691)
-
- Closing in favor of [Feature #21800]
-
- When listing a directory, it's very common to need to know the type of each children, generally because you want to scan recursively.
The naive way to do this is to call `stat(2)` for each children, but this is quite costly.
This us... -
06:59 AM Bug #21799: Delegated top-level methods are not visible outside the Ruby Box
- I think `box.Foo.say` should be `box::Foo.say`. https://github.com/ruby/ruby/pull/15690
-
06:38 AM Bug #21799 (Closed): Delegated top-level methods are not visible outside the Ruby Box
- The following example code based on Ruby Box results in an unexpected error.
https://github.com/ruby/ruby/blob/v4.0.0-preview3/doc/language/box.md#top-level-methods
I'm not familiar with Ruby Box, but it seems that either the above d... -
- * Escape unexpected links
* Remove unnecessary path name from in-file reference -
- To avoid the misconception that previously conditional code had to be
written on a single line.
12/21/2025
-
-
-
-
-
-
-
- 06:26 PM Revision d0ec60dc (git): More doc improvements to ractor.md (#15676)
- [DOC] More doc improvements to ractor.md
-
- https://github.com/ruby/mmtk/commit/c4cca6c1c3
-
- 09:35 AM Revision 2ffd5ad0 (git): [DOC] Remove duplicate Pathname promotion entry at NEWS.md
- The Pathname promotion to core class is already documented in the
"Core classes updates" section, making this duplicate entry
redundant. -
- Adding a fast path for bump pointer allocator can improve allocation
performance.
For the following microbenchmark with MMTK_HEAP_MIN=100MiB:
10_000_000.times { String.new }
Before:
810.7 ms ± 8.3 ms [User: 790.9 ms, Sys... -
- * Align "Contains" column in "Streams" table
* Align some columns vertically
* Remove a duplicate `$-a` description -
12/20/2025
-
- Shape tree pollution could cause this test to flake.
-
- Defining ivars in initialize method guarantees the object to be embedded.
-
-
-
-
- 08:28 PM Revision 3fee7dd9 (git): Small improvements to doc/language/ractor.md (#15588)
- [DOC] Improvements to doc/language/ractor.md
-
- https://github.com/ruby/mmtk/commit/2185189df4
-
- If the slot_size < RVALUE_SIZE then we would underflow in the memset.
-
- * [DOC] Enhancements for globals.md
-
03:16 PM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- Thank you for your comments. Let me summarize the discussion.
### 1. Introducing a new API under `Etc`
Introducing a method such as `Etc.cpu_quota`, which returns `Float | nil`, seems reasonable.
### 2. Changing the behavior of ... -
11:41 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- CPU quotas can be floating point numbers though, not just integers.
But `Etc.nprocessors` returns an Integer.
So it seems having a new method is worth it.
I think it's good if `Etc.nprocessors` rounds it though for convenience and s... -
- osyoyu (Daisuke Aritomo) wrote in #note-4:
> It'd be nice if `RUBY_MAX_CPU` would be autoconfigured based on this, just like Go 1.25 `GOMAXPROCS`.
> ...
This sounds very good, but it should probably be a separate ticket though.
nobu... -
- How about https://github.com/ruby/etc/tree/linux-cgroup-from-maxprocs?
-
- This will allow the Ruby backtrace, memory mapping, etc. to be outputted
when a Ruby mutator thread panics.
https://github.com/ruby/mmtk/commit/d10fd325dd -
01:25 PM
Bug #21792 (Closed): 4.0.0-preview3: Build fails with `--with-ext=` when ENABLE_SHARED=yes: ruby/digest.h not found for rubyspec CAPI extensions
- Applied in changeset commit:git|e6520de3442659def3463d3bfdca3432f41b2d6a.
----------
[Bug #21792] Build rubyspec-capiext only when excuting `test-spec`
rubyspec-capiext is only needed for running specs, not for building or
installing R... -
- Do you then use this "minimal Ruby" to run the gem extconf.rb?
I don't think that works in general without extensions, extconf.rb can assume the full stdlib to be available.
As nobu said even RubyGems cannot load without `monitor`, a C... -
- mdalessio (Mike Dalessio) wrote in #note-6:
> Ah, I see, is this because logger relies on monitor, and logger is no longer part of the stdlib (it is a bundled gem)?
Not `logger`, `lib/rubygems/core_ext/kernel_require.rb` requires `mo... - 01:24 PM Revision e6520de3 (git): [Bug #21792] Build rubyspec-capiext only when excuting `test-spec`
- rubyspec-capiext is only needed for running specs, not for building or
installing Ruby. -
-
- `Dir.mktmpdir` concatenates a random base-36 number separated by "-",
so may generate pathnames containing "-j4". -
- osyoyu (Daisuke Aritomo) wrote in #note-3:
> @eregon I'm not sure I fully understand your point, but conceptually your code should raise an `Ractor::IsolationError` by accessing a unshareable, mutable variable `a`.
You can try the ex... -
05:57 AM Feature #21767: Consider procs which `self` is Ractor-shareable as Ractor shareable
- I think a number of "frozen Proc" is enough small so the incompatibility is enough small to ignore.
So I'm +1.
-
-
- * Document Range#to_set
* Update Thread#raise and Fiber#raise signatures and docs
* Add reference to String#strip to character_selectors.rdoc
* Update *nil docs when calling methods
* Enhance Array#find and #rfind docs
* Add a notic... -
08:21 AM Bug #21798 (Open): `bundle install` command fails if touches `$LOAD_PATH` on `Ruby::Box` enabled
- ## How to reproduce
```dockerfile
FROM ruby:4.0.0-preview3-trixie
WORKDIR /ruby_box_test
RUN bundle gem foo --test=minitest
WORKDIR /ruby_box_test/foo
RUN head -n 10 foo.gemspec
# PASS
RUN bundle install
# PASS
RUN ... -
- https://bugs.ruby-lang.org/issues/21785#note-10
> It is too late to introduce it in Ruby 4.0, let's aim for 4.1.
This reverts commits:
* d0b72429a93e54f1f956b4aedfc25c57dc7001aa
Add support for signed and unsigned LEB128 to pack/unpa... - 07:18 AM Revision 49f9c9bf (git): Box: [DOC] Uodate the name from Namespace
-
- It is too late to introduce it in Ruby 4.0, let's aim for 4.1.
Matz. -
-
- This appears to be a workaround for Windows XP behavior. It is unnecessary now.
-
-
-
02:27 AM Revision bb0637a9 (git): ZJIT: [DOC] Fix link to in-repo file. Mention GNU Make requirement
-
- Unfortunately, with the information available, there is not much we can do on our end.
The PendingBranchRefs in question are transient reference counted objects in YJIT. They have clear
release points that should have been reached be...
12/19/2025
-
- https://github.com/ruby/mmtk/commit/ed9036c295
-
- https://github.com/ruby/mmtk/commit/4e789e118b
-
-
-
08:06 PM Revision d9c0d4c7 (git): Don't copy invalidated CME in rb_vm_cc_table_dup
- The cc_entries list associated with the invalidated CME can be deleted
from the table during GC, so it isn't safe to copy (and we shouldn't
copy it anyways, it's stale data). -
- > Why a new parameter?
because I misread the ticket, I didn't notice the `o`.
I do think `^` for offset is pure genius though. -
05:22 PM Feature #21796: unpack variant that returns the final offset
- I really like this idea. @jhawthorn suggested `^` instead of `o` though, and I really like it.
```ruby
bytes = "\x01\x02\x03"
offset = 0
leb128_value1, offset = bytes.unpack("R^", offset: offset) #=> 1
leb128_value2, offset = byt... -
- It would be useful indeed, but I'm not sure a new method is the best way?
I think the simplest would be a new keyword parameter:
```ruby
offset, *values = bytes.unpack("Ro", offset: offset, return_offset:true)
```
Another poss... -
- mame (Yusuke Endoh) wrote in [#note-4](https://bugs.ruby-lang.org/issues/21785#note-4):
> It's a shame `unpack` doesn't tell you how many bytes it read. You'd probably want a `unpack` variant that returns the final offset too, or a spec... -
07:04 PM Bug #21266: YJIT GC safety crash with proc objects as block argument
- Backport PR for 3.3: https://github.com/ruby/ruby/pull/15657
-
-
05:32 PM Bug #21792: 4.0.0-preview3: Build fails with `--with-ext=` when ENABLE_SHARED=yes: ruby/digest.h not found for rubyspec CAPI extensions
- > > I don't think the installation script works with no extensions because it loads rubygems that require monitor
> ...
Ah, I see, is this because logger relies on monitor, and logger is no longer part of the stdlib (it is a bundled gem... -
- > I don't think the installation script works with no extensions because it loads rubygems that require monitor
@nobu Is this something that changed since Ruby 3.4? `rake-compiler` has been using the `--with-ext=` (empty) option since... -
- I don't think the installation script works with no extensions because it loads rubygems that require `monitor`.
- 12:58 PM Revision 8c7e6f24 (git): Update bundled gems list as of 2025-12-19
-
11:02 AM Revision e23a918a (git): Update NEWS.md for Fiber Scheduler (#15629)
-
- Previously, calling IO#flush or closing an IO with unflushed buffered
writes would just invoke `#blocking_operation_wait` and flush the write
buffer using a `write` syscall. This change adds flushing through the
fiber scheduler by invoki... -
- Applied in changeset commit:git|dd2f7d6ae6ab53bea7a179338378e1d32c306747.
----------
[Bug #21794] Fix for platforms where O_CLOEXEC is not available -
10:44 AM Bug #21794: O_CLOEXEC is not available on Solaris 10
- Yes, with the patch, it is successfully compiled without errors, and make test-all completed without any additional errors/failures.
-
- Can [GH-15650](https://github.com/ruby/ruby/pull/15650) fix it?
-
-
10:20 AM Bug #21696: Performance degradation for long running processes in Ruby 4.0.0-preview2
- @luke-gru FWIW 4.0.0-preview3 performs normally.
-
- I anticipated that we would consider this eventually, but incorporating it into the core presents significant challenges.
Here are two major issues regarding feasibility.
(Based on chats with @ko1, @tompng, and @yui-knk, though the... -
02:09 AM Feature #21795 (Open): Methods for retrieving ASTs
- I would like to propose a handful of methods for retrieving ASTs from various objects that correspond to locations in code. This includes:
* Proc#ast
* Method#ast
* UnboundMethod#ast
* Thread::Backtrace::Location#ast
* TracePoint#... -
09:13 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- It'd be nice if `RUBY_MAX_CPU` would be autoconfigured based on this, just like Go 1.25 `GOMAXPROCS`.
Its default value is currently fixed to 8, but not many cloud containers have 8 cores worth of processors.
https://github.com/ruby/... -
- RubyGems 4.0.x support -j option for building C extension gem. But It causes in container environment like Circle CI.
https://github.com/ruby/rubygems/issues/9170
If cgroup provides the correct number of CPU for Cicle CI or others... -
- Currently, `Etc.nprocessors` ignores cgroup CPU quotas. This causes issues in containers where CPU limits differ from the host CPU count.
I have written a gem for this purpose (https://github.com/moznion/maxprocs-ruby), but it would be ... -
- @eregon I'm not sure I fully understand your point, but conceptually your code should raise an `Ractor::IsolationError` by accessing a unshareable, mutable variable `a`. My proposal's intent was to preserve `self` while making the proc s...
-
-
- Since `Set#delete` is O(1) performance and return self, why not just:
```ruby
>> Set[1, 2, nil, 3].delete(nil)
=> Set[1, 2, 3]
``` -
- It seems hunging up.
-
- 06:44 AM Revision 47244b0f (git): Fix: Specifying 0 should cause an immediate timeout (#15641)
- This change fixes a bug in which specifying 0 for timeout-related options (such as the `timeout` option of `Addrinfo.getaddrinfo`) incorrectly results in an infinite wait.
(This change overwrites https://github.com/ruby/ruby/pull/15626 .) -
- Semicolon is optional however it clarifies the end of the rule.
-
-
- A placeholder to handle GNU make jobserver option.
spec/default.mspec didn't handle the jobserver using a FIFO. - 03:12 AM Revision 42d66b89 (git): Fix: Do not check open_timeout twice (#15626)
-
- 02:44 AM Revision b90d3a6b (git): Update bundled gems list as of 2025-12-19
-
- * Fix rbs test failure caused by minitest6
* Bundle minitest-6.0.0 -
- 12:59 AM Revision fec5363b (git): Update default gems list at 5c0c0dd8737c8225f0ebcf0eaf3fb8 [ci skip]
-
- https://github.com/ruby/prism/commit/21c499d6e4
-
12:58 AM Revision e2c886dd (git): [ruby/prism] Reject `p(p a, &block => value)` and similar
- Redo of https://github.com/ruby/prism/pull/3669 with more tests
https://github.com/ruby/prism/commit/48b403ea79 -
- https://github.com/ruby/prism/commit/138db9ccc4
-
- * assert_raise's 2nd argument is the failure message,
shown when the expected exception is not raised.
It's not the expected message.
See https://github.com/test-unit/test-unit/issues/347
https://github.com/ruby/prism/commit/e3df9... -
-
-
-
12/18/2025
-
-
-
-
- Applied in changeset commit:git|d0b72429a93e54f1f956b4aedfc25c57dc7001aa.
----------
Add support for signed and unsigned LEB128 to pack/unpack.
This commit adds a new pack format command `R` and `r` for unsigned and
signed LEB128 encod... -
- mame (Yusuke Endoh) wrote in #note-6:
> That apparoach is unreliable because LEB128 is redundant. For example, both `"\x03"` and `"\x83\x00"` are valid LEB128 encodings of the value 3.
Ah of course. I didn't think about that. 🤦♀️ -
- > You could tell how many bytes you read based on the size of the leb128_value returned.
That apparoach is unreliable because LEB128 is redundant. For example, both `"\x03"` and `"\x83\x00"` are valid LEB128 encodings of the value 3.
... -
- This commit adds a new pack format command `R` and `r` for unsigned and
signed LEB128 encoding. The "r" mnemonic is because this is a
"vaRiable" length encoding scheme.
LEB128 is used in various formats including DWARF, WebAssembly, MQ... -
- Co-authored-by: Alan Wu <alanwu@ruby-lang.org>
-
- Co-authored-by: Alan Wu <alanwu@ruby-lang.org>
YJIT: Support calling bmethods in Ractors
Co-authored-by: Luke Gruber <luke.gru@gmail.com>
Suggestion from Alan -
- Co-authored-by: Luke Gruber <luke.gru@gmail.com>
-
- This is easier to access as ec->ractor_id instead of pointer-chasing through
ec->thread->ractor->ractor_id
Co-authored-by: Luke Gruber <luke.gru@gmail.com> - 08:42 PM Revision aace29d4 (git): Check for NULL fields in TYPEDDATA memsize functions (#15633)
- Some TYPEDDATA objects allocate struct fields using the GC right after
they get created, and in that case the VM can try to perform a GC and join
a barrier if another ractor started one. If we're dumping the heap in another
ractor, this ... - 08:08 PM Revision a7eb1879 (git): [DOC] small improvements to ractor class docs (#15584)
- * Ractor.yield no longer exists
* Ractor.shareable_proc returns a copy of the given proc
* Improve wording for monitoring/unmonitoring ports -
- Applied in changeset commit:git|fb1dd92d30a8df93f6fe2746aacc097f4c3ea62b.
----------
thread_sync.c: rename mutex_trylock internal function
[Bug #21793]
To fix a naming conflict on solaris. -
- On Solaris, with GCC 7.5.0, failed to compile thread.c with "error: conflicting types for 'mutex_trylock'".
On Solaris, the function name mutex_trylock(3C) is already used by the OS.
https://docs.oracle.com/cd/E88353_01/html/E37843... -
- [Bug #21793]
To fix a naming conflict on solaris. -
- Allows to remove some duplicated code like szqueue_length, etc.
-
- If the queue was allocated without calling initialize,
`ary` will be `0`. -
- We receive the ec as argument, it's much cheaper to pass it
around that to look it up again. -
- Previously when using a JIT and Ractors at the same time with debug
assertions turned on this could rarely fail with:
vm_core.h:1448: Assertion Failed: VM_ENV_FLAGS:FIXNUM_P(flags)
When using Ractors, any time the VM lock is acquir... - 06:51 PM Revision 74bfb160 (git): Remove assertion in encoded_iseq_trace_instrument (#15616)
- `encoded_iseq_trace_instrument` is safe to call in a ractor if the iseq
is new. In that case, the VM lock is not taken. This assertion was added in
4fb537b1ee28bb37dbe551ac65c279d436c756bc. -
06:39 PM Bug #21790: `Socket.getaddrinfo` hangs after `fork()` on macOS 26.1 (Tahoe) for IPv4-only hosts
- Ah my earlier Python script had a bug.
My initial Python test incorrectly reported success. The script used `os.WEXITSTATUS()` to check the child's exit status, but this function only works for processes that exit normally. When a pro... -
- Thank you. This looks like the same issue reported multiple times in the past, but we were previously stuck without a way to investigate.
https://bugs.ruby-lang.org/issues/15490
https://bugs.ruby-lang.org/issues/15794
https://github... -
- mame (Yusuke Endoh) wrote in #note-3:
> Thank you for the report.
> ...
Ah yes, sorry I should have clarified this in my post. I tested this in 3.2.6 but it manifests differently in that version.
When I ran the same reproduction script ... -
- Thank you for the report.
Since I don't have access to Tahoe, I cannot test this in my own environment. However, I have a few questions to clarify the situation.
The change to perform DNS lookups in a dedicated background thread wa... -
- We never need the actual thread object and this avoid any issue
if the thread object is ever moved. -
- Because O_CLOEXEC is not available on Solaris 10, an error occurs when compiling box.c: "'O_CLOEXEC' undeclared (first use in this function)"
```
gcc -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -O3 -fno-fast-math ... - 05:37 PM Revision bfd28d58 (git): make rb_singleton_class ractor safe (#15591)
- Since singleton classes are created lazily, we need to make sure that
we lock around their creation. Unfortunately, that means we need to
lock around every shareable object's call to `singleton_class`,
including classes and modules. -
- This improves several enhancements to the Aliki theme. And since Aliki
also became the default theme, we don't need to specify the generator name
anymore. -
01:28 PM Bug #20699: On Windows, the `__dir__` keyword is garbled in paths containing Japanese characters, and `require_relative` fails as well
- There is a fix available since one year, but no feedback at all. That makes it difficult to contribute anything: https://github.com/ruby/ruby/pull/12377
-
11:01 AM Bug #21049: Reconsider handling of the numbered parameters and "it" parameter in `Binding#local_variables`
- Thank you for the new methods!
-
- I have tried for curiosity with `ruby 4.0.0preview3` and it is still unfixed:
```
$ RUBY_BOX=1 ruby -ve 'ns = Ruby::Box.new; p ns::Gem.equal?(Gem)'
ruby 4.0.0preview3 (2025-12-18 master cfa3e7cf75) +PRISM [x86_64-linux]
ruby: warning... - 07:47 AM Revision 9f266ae6 (git): Update default gems list at 0e85881e0cded6ec82ef105b5ff2d0 [ci skip]
-
- https://github.com/ruby/delegate/commit/90ffceb6d6
-
- This reverts commit 02e4b58b615d0dd83a6af5cd7c2b8861724011ee.
-
- This reverts commit 6e0f2b31f0f4a2a942f3c1daad1bb64852fe6815.
-
- https://github.com/ruby/delegate/commit/aef34e8c8b
- 07:46 AM Revision e6ca8908 (git): Allow use of DelegateClass in ractor
- Use `eval` instead of `define_method` when defining delegate methods for
`DelegateClass`. -
- This reverts commit https://github.com/ruby/delegate/commit/fc2bd0498af0.
https://github.com/ruby/delegate/commit/7d5c1e0842
Co-authored-by: Jean Boussier <byroot@ruby-lang.org> -
- https://github.com/ruby/delegate/commit/fa35b20eca
- 07:46 AM Revision 01e9f95c (git): [ruby/delegate] Allow use of DelegateClass in ractors
- Tempfile uses DelegateClass and Tempfile should be able to be used
by different ractors.
https://github.com/ruby/delegate/commit/cad194260b -
- Fix a `-Wint-in-bool-context` warning.
```
proc.c:688:33: warning: '?:' using integer constants in boolean context [-Wint-in-bool-context]
688 | if (RBOOL(get_local_variable_ptr(&env, idItImplicit, FALSE))) {
``` - 07:39 AM Revision 74b18b53 (git): Bump github.com/microsoft/vcpkg from master to 2025.12.12
- Bumps [github.com/microsoft/vcpkg](https://github.com/microsoft/vcpkg) from master to 2025.12.12. This release includes the previously tagged commit.
- [Release notes](https://github.com/microsoft/vcpkg/releases)
- [Commits](https://gith... -
05:22 AM Revision 769c6a1c (git): [DOC] Use Arrays in examples for Array#find
-
- * `rb_intern_str`: the argument must be `T_STRING`, no conversion.
* `rb_intern_str`, `rb_check_id`, `rb_to_id`, `rb_check_symbol`: raise
`EncodingError` unless the "name" argument is a valid string in its
encoding. -
- 12:34 AM Revision cfa3e7cf (git): [DOC] Fix double-word typos in comments
- Found via `grep` for repeated words.
* set.c: Fix "or or"
* include/ruby/internal/symbol.h: Fix "is is"
* include/ruby/internal/ctype.h: Fix "in in"