Activity
From 10/25/2025 to 10/31/2025
Today
-
02:28 AM Revision 8b1fd559 (git): [ruby/net-http] v0.7.0
- https://github.com/ruby/net-http/commit/ec9c70a6fb
- 01:50 AM Revision 78966ae6 (git): Update default gems list at d2ffab11ce629367b13e7b607b9644 [ci skip]
-
- https://github.com/ruby/uri/commit/c41903b3e4
-
01:38 AM Revision f0993de1 (git): [ruby/uri] improve error message
- https://github.com/ruby/uri/commit/1c6e81b721
-
01:38 AM Revision 1dce0ae5 (git): [ruby/uri] Switch a parsing behavior completely when switching a parser
- Currently, some methods' behavior(e.g. `URI.parse`) don't change
when switching a parser. This is because some methods use
`DEFAULT_PARSER`, but `parser=` doesn't change `DEFAULT_PARSER`.
This PR introduces a constant to keep a parser's... - 01:38 AM Revision 08e822ba (git): [ruby/uri] chore(docs): replace reference to the obsolete URI.escape with URI::RFC2396_PARSER.escape
- https://github.com/ruby/uri/commit/72e7d6b364
-
- https://github.com/ruby/uri/commit/1fc4f0496a
-
- 12:15 AM Revision 17e95cb4 (git): Update default gems list at 94e6d76714a4dc784cde503c846998 [ci skip]
-
- https://github.com/ruby/English/commit/c921886aaf
-
12:13 AM Revision a4c33615 (git): [ruby/mmtk] Bump mmtk-core
- https://github.com/ruby/mmtk/commit/9876d8f0a1
10/30/2025
- 10:31 PM Revision f8b4feb7 (git): ZJIT: Use LoadField for specialized GetIvar
- 10:31 PM Revision 0268c86b (git): ZJIT: Inline struct aref
-
10:23 PM Revision c54faf29 (git): release.yml: Use workflow_dispatch for docker-images
- instead of repository_dispatch.
Only that workflow reacts to repository_dispatch, so just using
workflow_dispatch should be enough. We want to use workflow_dispatch for
manual triggers, and I don't want to maintain two different dispatc... -
10:14 PM Revision 69ec1481 (git): ZJIT: Count unsupported fancy caller side features
- These count caller-side features we don't support. But because we side
exit when we see them through unhandled_call_type(), these new counters
currently don't trigger. -
- In cases we fall back when the callee has an unsupported signature, it
was a little inaccurate to use `send_fallback_send_not_optimized_method_type`.
We do support the method type in other situations.
Add a new `send_fallback_fancy_call... - 10:02 PM Revision 68dd1abd (git): ZJIT: Run ruby-bench as a test suite (#15003)
-
09:14 PM Revision 2afcdc69 (git): Change load factor of concur. set from 0.5 to 0.75 (#15007)
- Before, the 50% load factor was not working correctly with the new capacity
calculation on resize and too many resizes were seen.
Before this change
------------------
Example:
old_capacity = 32
old_size = 16
deleted_entries = 2 (almo... -
08:47 PM Revision 34b0ac68 (git): ZJIT: Prevent specialization of splats instead of side-exiting (#15005)
-
08:45 PM Bug #21560 (Closed): RUBY_MN_THREADS=1 causes large performance regression in Puma 7
- This should be fixed by https://github.com/ruby/ruby/commit/0531fa4d6fea100f69f0bac9e03973fe49ecd570
-
08:44 PM Revision 0531fa4d (git): mn timer thread: force wakeups for timeouts
-
08:35 PM Bug #21654: Set#new calls extra methods compared to previous versions
- > If an operation hangs, let it hang.
I don't agree with that. If an operation crashes, yes, let it crash. But if it hangs, that's an order of magnitude or two harder to debug. Even more so if the "hang" is accompanied by unrestrained m... -
04:36 PM Bug #21654: Set#new calls extra methods compared to previous versions
- tenderlovemaking (Aaron Patterson) wrote in #note-10:
> mame (Yusuke Endoh) wrote in #note-9:
> ...
I agree with @mame and @tenderlovemaking. Removing special handling of infinite ranges avoids the original issue (calling `size`), as ... -
04:29 PM Bug #21654: Set#new calls extra methods compared to previous versions
- mame (Yusuke Endoh) wrote in #note-9:
> Dan0042 (Daniel DeLorme) wrote in #note-7:
> ...
I personally agree with this. If I write an infinite loop, I expect it to loop infinitely, even if I wrote the infinite loop by mistake. Calling... -
04:20 PM Bug #21654: Set#new calls extra methods compared to previous versions
- Dan0042 (Daniel DeLorme) wrote in #note-7:
> What that really what you meant by "checking if Range#end is nil is good enough" ?
Yes. The original issue (#21513) was about the consistency between `(1..).to_a` and `(1..).to_set`. Since... -
02:52 PM Bug #21654: Set#new calls extra methods compared to previous versions
- IMO, ranges should behave the same when `end == Float::INFINITY` and when `end == nil`. They are both practically endless ranges, but nothing normalizes them so that they always behave the same. Maybe `(1..1/0.0)` should be internally tr...
-
- @mame, this PR causes `Set.new(1..1/0.0)` to hang rather than raise an error. The unit test for this was removed: https://github.com/ruby/ruby/pull/14990/files#diff-841852fda8de5c29b86810572be72d6e29cda4a2f3d179c63b77fb6fb06d09dfL91-L93
... -
07:15 PM Revision 6707945f (git): ZJIT: Split out optimized method types in stats (#15002)
- We can see send/block call/struct aref/... e.g. on lobsters:
```
Top-9 not optimized method types for send_without_block (100.0% of total 3,133,812):
iseq: 2,004,557 (64.0%)
optimized_struct_aref: 496,232 (15.8%)
... -
-
- Right now we have a subtle type system bug around `types::Class`. Until
that is resolved, stop marking `Kernel#class` as returning
`types::Class`, which fixes Rubocop.
Re: https://github.com/Shopify/ruby/issues/850 -
01:32 PM Revision 481f9944 (git): [Feature #19630] Limit the versions with the old behavior
- It is already declared as:
> This behavior is slated to be removed in Ruby 4.0 -
- Applied in changeset commit:git|244a37bd53fb5c7ba219ef958b6adaa2c4b0b67e.
----------
Fixes [Bug #21522] eval isolation in Ractors for Prism -
-
01:15 PM Bug #21618 (Closed): Allow to use the build-in prism version to parse code
-
- In the case of attribute writes, there are use cases where you want
to know the location of the = sign. (Internally we actually need
this for translation to the writequark AST.)
https://github.com/ruby/prism/commit/bfc798a7ec -
01:05 PM Revision 99382f74 (git): [ruby/prism] Unescape unary method calls
- Followup to https://github.com/ruby/prism/pull/2213
Before:
```sh
$ ruby -ve "puts 42.~@"
ruby 3.4.6 (2025-09-16 revision https://github.com/ruby/prism/commit/dbd83256b1) +PRISM [x86_64-linux]
-e:1:in '<main>': undefined method '~@' for... -
-
-
-
12:00 PM Bug #21607: require 'concurrent-ruby' causes segfault with Ruby 3.4.6 on linux/i686 built with GCC 15
- thesamesam (Sam James) wrote in #note-15:
> Is there a backtrace for this somewhere?
Ruby was segfaulting without creating a backtrace. -
09:30 AM Bug #21607: require 'concurrent-ruby' causes segfault with Ruby 3.4.6 on linux/i686 built with GCC 15
- Is there a backtrace for this somewhere?
-
10:56 AM Revision 3ca43216 (git): [ruby/json] Add ryu float parser.
- https://github.com/ruby/json/commit/9c4db31908
Co-Authored-By: Jean Boussier <jean.boussier@gmail.com> -
10:34 AM Revision 317f102c (git): [ruby/json] Fix GeneratorError messages to be UTF-8 encoded
- https://github.com/ruby/json/commit/965ba6c5d4
-
- Reminds me a bit of https://bugs.ruby-lang.org/issues/21516 as well.
-
- alanwu (Alan Wu) wrote in #note-8:
> Looks like you're not building with LTO, so the miscomp from `ipa-modref` should be in rb_str_resize(). That should be enough for a bug report for GCC, since they [need](https://gcc.gnu.org/bugs/#need... -
- Looks like you're not building with LTO, so the miscomp from `ipa-modref` should be in rb_str_resize(). That should be enough for a bug report for GCC, since they [need](https://gcc.gnu.org/bugs/#need) a preprocessed C file.
Maybe thi... -
- 09:15 AM Revision d1d85bb4 (git): [ruby/resolv] Fix invalid "Broken registry" warning for UseDomainNameDevolution
- This value is dword, not a string.
Amends https://github.com/ruby/resolv/commit/720e25034042.
https://github.com/ruby/resolv/commit/bf00ed8585 -
09:04 AM Revision 3f230c7e (git): add deps
-
-
- `cross_ractor_require` is sharable object but it refers
to unsharable objects.
To fix it, make the process simple. -
-
-
-
-
- 06:53 AM Revision 6b9b048a (git): Update bundled gems list as of 2025-10-30
-
- @Earlopain Thanks for your confirmation. I fixed that at `ruby/resolv` and `ruby/ruby`.
-
- Applied in changeset commit:git|15f2dcceb4787c5738dde48f580019c3765ce1b8.
----------
[ruby/resolv] Fallback to powershell implementation under the bundle environment
[Bug #21645]
win32-registory can't load fiddle if Gemfile didn't hav... -
- [Bug #21645]
win32-registory can't load fiddle if Gemfile didn't have that dependency.
https://github.com/ruby/resolv/commit/1319183a4b -
- For test_zjit.rb output, it was too long for a single test to print
thousands of lines. -
- I wanted to see comments on test_zjit.rb failures.
-
- This commit fixes the case when there are multiple missing or incorrect
keywords provided to a method. Without this fix, ErrorHighlight itself
will raise an exception
https://github.com/ruby/error_highlight/commit/8bde92b36e -
12:35 AM Revision 750c7509 (git): [DOC] ZJIT: Add documentation about native stack and Ruby's VM stack (#14993)
- ZJIT: Add documentation about native stack and Ruby's VM stack
-
- The following script leaks memory:
10.times do
100_000.times do
"\ufffd".encode(Encoding::US_ASCII, fallback: proc { "\uffee" })
rescue
end
puts `ps -o rss= -p #{$$}`
end
Before:
451196
...
10/29/2025
-
11:53 PM Bug #21655: segfault when building 3.3.10, regression from 3.3.9
- alanwu (Alan Wu) wrote in #note-5:
> It's surprising that leaving the temporary struct uninitialized avoids the crash. Smells like a GCC bug or some UB on our end the optimizer is exploiting.
> ...
Per a suggestion on the downstream bu... -
- alanwu (Alan Wu) wrote in #note-5:
> It's surprising that leaving the temporary struct uninitialized avoids the crash. Smells like a GCC bug or some UB on our end the optimizer is exploiting.
> ...
It doesn't appear to, when added to C... -
- It's surprising that leaving the temporary struct uninitialized avoids the crash. Smells like a GCC bug or some UB on our end the optimizer is exploiting.
Does `./configure optflags=-fno-strict-aliasing ...` help? -
- I manually bisected inside that "bad" commit and found that this minimal diff on top of v3_3_10 eliminates the build failure:
```
diff --git a/include/ruby/internal/core/rstring.h b/include/ruby/internal/core/rstring.h
index 9cf9daa... -
- Thank you for fixing the markdown in the comment 0.
On an affected machine, I was able to bisect the git repo between tags v3_3_9 and v3_3_10:
```
5a8d7642168f4ea0d9331fded3033c225bbc36c5 is the first bad commit
commit 5a8d7642168f... -
- backtrace using a gentoo-built build with -ggdb3 added to CFLAGS
```
beans ~ # cd /var/tmp/portage/dev-lang/ruby-3.3.10/work/ruby-3.3.10/
beans /var/tmp/portage/dev-lang/ruby-3.3.10/work/ruby-3.3.10 # gdb --args ./miniruby -I./lib -... -
- ref downstream bug https://bugs.gentoo.org/965095 - reporting upstream because I was able to reproduce the problem from ruby-3.3.10.tar.xz manually
build log excerpt; the rest will be provided as an attachment
```
gcc -O2 -pipe -m... -
- I'm seeing some memory corruption in the wild on blocks in
`IseqPayload::dead_blocks`. While I unfortunately can't recreate the
issue, (For all I know, it could be some external code corrupting YJIT's
memory.) establishing a link between... -
- so that it can be easily specified with `--zjit-dump-lir=`.
-
-
-
-
-
-
- mame (Yusuke Endoh) wrote in #note-5:
> > How about handling only `Range` and `Enumerator` (not `Enumerable`) for now?
> ...
I sent a pull request that only handles `Range` for now: https://github.com/ruby/ruby/pull/14990
This fixe... -
- > How about handling only `Range` and `Enumerator` (not `Enumerable`) for now?
I think it would be better to handle only Range for now, and not Enumerator either. See https://bugs.ruby-lang.org/issues/21513#note-10 -
- k0kubun (Takashi Kokubun) wrote in #note-1:
> How about handling only `Range` and `Enumerator` (not `Enumerable`) for now? Avoiding an extra DB query on ActiveRecord relations seems like a more important use case than preventing user-de... -
- It seems to me that's an argument in favor of #17924 `Range#infinite?`
-
- How about handling only `Range` and `Enumerator` (not `Enumerable`) for now? Avoiding an extra DB query on ActiveRecord relations seems like a more important use case than preventing user-defined `Enumerable` with an infinite length from...
-
- I'm trying to test Ruby 3.5.0 with our Rails application and we've found that `Set.new` is now causing extra database queries to happen.
The changes in d4020dd5faf call "size" on enumerable objects that are passed to the `new` method,... -
- With the commit from @andremuta:
Without RUBY_MN_THREADS:
```
Running 15s test @ http://localhost:9292
12 threads and 16 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 1.00ms 1.52ms 11.44ms 82.6... -
06:35 PM Misc #21656: Exclude dependabot PRs from automated gem release notes
- Earlopain (Earlopain _) wrote in #note-4:
> `net-imap` actually uses it already: https://github.com/ruby/net-imap/blob/079167e99b47957d53c71c927ebbca537aae39d1/.github/release.yml#L23. The name does need to be `dependabot[bot]` I think.... -
- Thanks both.
I will try that template at next gem release. -
- Yeah! I just found that as well: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes
I was thinking about something a bit more comp... -
- There is a configuration file to control which labeled PRs make it into the automated release notes and which ones should be excluded. I can help set that up if it will be helpful.
-
- > I removed them manually if I found that.
Ah, I didn't know that, thanks! I did check some other release notes and was surprised that they were often missing.
> ...
I will think about this 👍. Unfortunatly the cli itself doesn't ha... -
- I removed them manually if I found that.
If you have an idea to exclude that with `gh release create --generate-note`, I will add it to our release workflow.
-
- Ruby has many gems, and many of them have release notes generated with the github command line instead of being written by a human. Usually that is fine, I don't have much of a problem with that approach. But what is less ideal is that g...
-
- This reverts commit 02fd62895d9a13f56253521dedd80e39d4eafbb5.
It stopped working again. -
- 03:17 PM Revision fcd7da15 (git): ZJIT: Introduce a better LIR printer (#14986)
-
02:52 PM Misc #21657: Question: Is Ruby 4.0 planned for December 2025 or later?
- Thank you! The version number itself doesn’t affect anything on our side. Whether it’s released as 3.5 or 4.0, both are perfectly fine. I just wanted to make sure I’m not missing an extra release in between.
-
- It seems like the next version of Ruby will be branded as 4.0, but that is completely a decision for @matz to make as he wishes. Ruby version numbers don't follow semantic versioning, so 4.0 doesn't mean that there will be breaking chang...
-
- Thank you for the clarification!
I just wanted to make sure there isn’t another release already planned beyond 3.5. For example, a 4.0 version with some other significant changes.
If it’s purely a versioning matter and 3.5 remains th... -
- dmitry.pogrebnoy (Dmitry Pogrebnoy) wrote:
> Having a clear, public roadmap would really help library and tooling authors (like IDE vendors) prepare for upcoming versions and provide better support.
I'm curious what kind of problems ... -
- Hello Ruby core team,
I noticed that the first preview of Ruby 3.5 has been released, and at the same time there’s some talk in the community about Ruby 4.0 potentially arriving in December 2025.
Could you please clarify what the cur... -
- I implemented support for `Prism.parse(foo, version: "current")` in https://github.com/ruby/prism/pull/3679. This can be closed now from my perspective (I did not yet make use of that anywhere but plan to work on that)
-
-
- I approximatly applied your patch with the following in github ci:
```rb
- name: Patch
run: (Get-Content D:/rubyinstaller-head-x64/lib/ruby/3.5.0+4/win32/resolv.rb).Replace('LoadError', 'LoadError, Gem::MissingSpecError') ... -
- It should fallback to pwsh implementation under `bundle` environment.
```
diff --git ext/win32/lib/win32/resolv.rb ext/win32/lib/win32/resolv.rb
index 226de7cba36..dae53baf118 100644
--- ext/win32/lib/win32/resolv.rb
+++ ext/win3... -
-
- Assume that `FILETIME` and `ULARGE_INTEGER::u` are the same layout
actually. -
-
- `Time#nsec` and `Time#subsec` were both introduced in Ruby 1.9.
https://github.com/ruby/date/commit/2c310d9f5c -
- https://github.com/ruby/date/commit/fd8e3725f8
-
- Applied in changeset commit:git|12350eb9e0d3317da57b5a37c0c2810946b48850.
----------
[Bug #21625] Allow io/wait methods with `IO#ungetc` in text mode -
- https://github.com/ruby/ruby/pull/14985
-
-
- 07:36 AM Revision b55e9115 (git): Update default gems list at 8f0b9b27cec1ec187c6357586dc98d [ci skip]
-
- https://github.com/ruby/fileutils/commit/29de582f68
- 07:10 AM Revision b8f7c18a (git): Update default gems list at 337c4bc16384fa44f7a486d550461a [ci skip]
-
- https://github.com/ruby/date/commit/d535f7e85f
- 06:58 AM Revision bb5f5a52 (git): Update default gems list at 2dcf1f74a417c01c64f45f1ea73d93 [ci skip]
-
- https://github.com/ruby/timeout/commit/f42b47d383
- 06:31 AM Revision 582475b3 (git): Update default gems list at 4f223b72a9976cd015c4d926297c61 [ci skip]
-
- https://github.com/ruby/zlib/commit/5d50b223b1
-
-
-
-
- The fix introduced another inconsistency:
```
$ ruby -e 'Enumerator.new(Float::INFINITY) {|g| loop { g << 1 } }.to_set'
-e:1:in 'Enumerable#to_set': cannot initialize Set from an object with infinite size (ArgumentError)
fr... - 01:47 AM Revision 7bc72469 (git): [DOC] Update refinements.rdoc
- removes documentation for the activation order of `include` and `prepend` inside a refinement
-
-
- Applied in changeset commit:git|d17ce4bd05dc05d48f5f4bc75171fcebda1678ed.
----------
[Bug #21652] [DOC] Update unmarshalable object list
The `Data` mentioned here was the old `T_DATA` class, not the current
extended `Struct`. -
- The `Data` mentioned here was the old `T_DATA` class, not the current
extended `Struct`. -
-
- Allow instructions to constrain their operands' input types to avoid
accidentally creating invalid HIR.
10/28/2025
-
11:48 PM Revision 80be97e4 (git): ZJIT: Fill `cfp->pc` with trap value for C methods in debug builds
-
- This prevents a generic RuntimeError from being raised so we can ensure
that the correct error is being rescued. -
- The method and aref cases need to accept a parameter.
-
-
- 10:25 PM Revision 8dc276f3 (git): Bump github.com/microsoft/vcpkg from master to 2025.10.17
- Bumps [github.com/microsoft/vcpkg](https://github.com/microsoft/vcpkg) from master to 2025.10.17. This release includes the previously tagged commit.
- [Release notes](https://github.com/microsoft/vcpkg/releases)
- [Commits](https://gith... - 10:24 PM Revision 5a14999d (git): Bump actions/upload-artifact from 4 to 5
- Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 5.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v4...v5)
---
... -
09:36 PM Feature #21653 (Open): Unify Hash methods and preserving default/default_proc
- All the Hash methods that return a new instance of Hash don't preserve the `default` and `default_proc` properties except `#compact` and `#merge`:
```ruby
h = {a: 1}
h.default = 0
h.compact[:f] == 0 # => true
h.merge(b: 2)[:... - 08:47 PM Revision afb0d431 (git): ZJIT: Drop --seed from test-all on CI (#14976)
-
- Eregon (Benoit Daloze) wrote in #note-27:
> If the gem is a noop then of course it would not matter, but I'm unsure if the gem should be a noop.
I can't answer if it "should", but at least that's how it works with `set`, so at least ... -
07:02 PM Bug #21640: Core Pathname is missing 3 methods / is partially-defined
- If the gem is a noop then of course it would not matter, but I'm unsure if the gem should be a noop.
There is also the issue that core already uses the pathname C extension, and loading the gem pathname C extension might cause issues, i... -
- Ah, thank you very much, now I see it.
So this #4 issue could be solved by implementing the 3 methods as shims that load the necessary dependencies, which then allows pathname to do `rb_provide("pathname.rb")` -
- Dan0042 (Daniel DeLorme) wrote in #note-24:
> So the issue here is that pathname doesn't use this `rb_provide` ?
pathname does use `rb_provide`:
```
$ git grep rb_provide pathname.c
pathname.c: rb_provide("pathname.so");
```... -
- > It's normal behavior when moving from stdlib to core that `rb_provide` is used to make it appear that the library has already been loaded. Having `set.rb` in `$"` makes it so code that uses `require 'set'` does not cause files to be lo...
-
- Dan0042 (Daniel DeLorme) wrote in #note-19:
> But _why_? If there's an actual problem with this approach I would like to hear it. If it's just because it "feels unclean" then I would like the core team to prioritize usefulness over these... -
- Dan0042 (Daniel DeLorme) wrote in #note-21:
> But that doesn't happen with `require "set"`. In fact, the "set" gem appear to never be loaded at all?! Sorry, I can't make sense of these divergent behaviors.
It's normal behavior when m... - 08:18 PM Revision d0c7234b (git): ZJIT: Support ParallelMov into memory (#14975)
-
- https://github.com/ruby/ruby/actions/runs/18887695798/job/53907237061?pr=14975
-
-
06:51 PM
Feature #20205: Enable `frozen_string_literal` by default
- ______________________________________________
-
- matz (Yukihiro Matsumoto) wrote in #note-75:
> Probably we would have Ruby4.0 in 2025, but I am not going to make frozen-string-literal default this year.
That's unfortunate, but OTOH it makes sense because first we need to make the ... -
- * [Feature #20205] Enable `frozen_string_literal` by default (eregon)
* Let's decide in which release the chilled string deprecation warning shows up regardless of verbosity level (R1) to make progress on this. How about 4.0?
* Oth... -
- `hir.rs` was getting rather large, so I've opted to move the inline tests into their own files. This should also help when looking for where to put your tests, as the optimization tests have a dedicated file.
Future follow up work could... - 05:37 PM Revision a9d42f7c (git): ZJIT: Print percentage of GuardType failure
- 05:37 PM Revision 2c90da46 (git): ZJIT: Count GuardType instructions
- We can measure how many we can remove by adding type information to C
functions, etc. -
05:08 PM Bug #21652 (Closed): Marshal#dump documentation out-of-date/unclear regarding Data class
- With the introduction of the `Data` class in Ruby 3.2, the `Marshal#dump` documentation is confusing since it claims that "Marshal can’t dump ... an instance of ... Data". It is even cross-linked to the new `Data` class. However, and tha...
-
-
-
-
- Once we add register spill, the C stack will have not only spilled basic
block params but also spilled VRegs.
We won't know how many stack slots are used for spilled VRegs until
alloc_regs, so you can't compute an offset as of writing LIR. -
-
-
- It's a call_threshold: 2 test
https://github.com/ruby/ruby/pull/14933#discussion_r2469731499 -
- Fixes https://github.com/Shopify/ruby/issues/814
This change specializes the case of calling `Array#pop` on a non frozen array with no arguments. `Array#pop` exists in the non-inlined C function list in the ZJIT SFR performance burndown... - 02:49 PM Revision 2e2f31c8 (git): ZJIT: Add IsBitNotEqual and inline BasicObject#!=
- 02:49 PM Revision c2bef01b (git): ZJIT: Optimize Kernel#===
- 02:49 PM Revision e973baa8 (git): ZJIT: Add BoxBool and remove CCall from BasicObject#==
- 02:49 PM Revision a4f8afce (git): ZJIT: Use FnProperties::default()
- 02:49 PM Revision 2a6e5d7d (git): ZJIT: Allow both inlining and annotating properties
- 02:49 PM Revision 74255204 (git): ZJIT: Remove redundant annotation
- 02:49 PM Revision 3624031b (git): ZJIT: Inline Kernel#nil? and NilClass#nil?
- We can fully remove the CCall now.
-
-
- https://github.com/ruby/rubygems/commit/c3cc38c72c
-
- https://github.com/ruby/rubygems/commit/e9bd59699c
-
- https://github.com/ruby/rubygems/commit/6fbbde48e2
-
- https://github.com/ruby/rubygems/commit/81dbd42abf
-
- https://github.com/ruby/rubygems/commit/15e46a3a68
-
- https://github.com/ruby/rubygems/commit/55745ee0f8
-
- From [String@Substitution+Methods]:
> Note that <tt>\\\\</tt> is interpreted as an escape, i.e., a single backslash.
> ...
This is what happens at the first line.
Since a space after a backslash is not a valid escape, the result a... -
09:10 AM Bug #21651 (Feedback): replacing a string with one backslash with two backslashes
- ruby 2.7.8p225 (2023-03-30 revision 1f4d455848) [x86_64-linux]
ruby 3.4.4 (2025-05-14 revision a38531fd3f) +PRISM [x86_64-linux]
```
irb(main):002> "\\".gsub("\\", "\\\\")
=> "\\"
irb(main):003> "\\".gsub("\\", "\\ \\")
=> "\\ \\... -
10:11 AM Feature #21650: Performance regression: Rational#floor(ndigits) extremely slow for huge ndigits in Ruby 3.4 (ok in 3.2)
- Sure, thanks for clarification and fast reply.
-
- Thank you for your reply.
I found a clearer case:
```ruby
p Rational(1, 3).floor(2**1) #=> (33/100)
p Rational(1, 3).floor(2**2) #=> (3333/10000)
p Rational(1, 3).floor(2**3) #=> (33333333/100000000)
p Rational(1, 3).floor(2**4... -
- mame (Yusuke Endoh) wrote in #note-3:
> Thank you for the report.
> ...
1. It wasn't involved in any production usage, we have fuzzy tests which generated this and it was in our test suite. Therefore I was surprised by performance degr... -
- Thank you for the report.
As the warning indicates, prior to Ruby 3.4 (up to 3.3), attempting to generate a huge `Integer` would return `Float::INFINITY`. Ruby 3.4 removed this inaccurate truncation, which is why it now takes longer. (#... -
- ## Summary
`Rational#floor(ndigits)` with a very large positive ndigits takes tens of seconds in Ruby 3.4, while it returns essentially instantly in Ruby 3.2. Reproducible on macOS and Linux. Looks like a missing fast‑path for rationals... -
- https://github.com/ruby/rubygems/commit/62ba34d6c9
-
08:28 AM Revision 7550f7e4 (git): [ruby/rubygems] Update new gem CoC and prompt
- Prompt wording "prefer safe, respectful, productive, and collaborative spaces" is copied verbatim from Ruby Community Conduct Guideline.
https://github.com/ruby/rubygems/commit/6cdf5f6d8a - 07:50 AM Revision aab390aa (git): [ruby/json] Use Vector API in the Java Extension
- Overview
This PR uses the [jdk.incubator.vector module](https://docs.oracle.com/en/java/javase/20/docs/api/jdk.incubator.vector/jdk/incubator/vector/package-summary.html) as mentioned in [issue #739](https://github.com/ruby/json/issues/... -
-
- C99 does not declare ways to designate the charset encoding of the
source file. We can assume just US-ASCII characters will be safe. -
04:07 AM Revision 02d53bab (git): [ruby/stringio] [DOC] Doc for StringIO#each_byte
- (https://github.com/ruby/stringio/pull/157)
https://github.com/ruby/stringio/commit/624ce56b4e
Co-authored-by: Sutou Kouhei <kou@cozmixng.org> - 03:58 AM Revision d864bd1a (git): Update default gems list at b3191d204b8b4fe4b29cf73cd09a1b [ci skip]
-
- https://github.com/ruby/erb/commit/e8d382a83e
- 03:50 AM Revision 4511e962 (git): Update default gems list at f7eee3427dcc8b644b9fd6c854f3e1 [ci skip]
-
- https://github.com/ruby/erb/commit/daa0e8712f
-
- (https://github.com/ruby/stringio/pull/159)
https://github.com/ruby/stringio/commit/6628d4837b
Co-authored-by: Sutou Kouhei <kou@cozmixng.org> -
- (https://github.com/ruby/stringio/pull/158)
https://github.com/ruby/stringio/commit/ec6bf815ae
Co-authored-by: Sutou Kouhei <kou@cozmixng.org> -
- I've finished to prepare Luke's account. Please let me know if you have any issues for developing Ruby.
-
- I've finished to prepare Stan's account. Please let me know if you have any issues for developping Ruby.
-
-
-
10/27/2025
-
- > The issue with `Pathname` is that it was not fully converted to core, only partially converted.
Yes that's the issue with the 3 methods missing from core Pathname, but @eregon's point 4 was about conflicts when `require "pathname"` ... -
- Dan0042 (Daniel DeLorme) wrote in #note-19:
> Doesn't `Set` have the same problems?
No.
> ...
In Ruby 3.2, `set` was default gem, and `Set` was an autoloaded constant. The `set` library was not required when a method was called (u... -
- > That's consensus with akr and me. We should avoid loading other libraries by simply calling methods from the embedded core classes.
But *why*? If there's an actual problem with this approach I would like to hear it. If it's just bec... - 10:57 PM Revision e5e32acc (git): ZJIT: Annotate Kernel#frozen? as returning BoolExact
- 10:57 PM Revision c3c25443 (git): ZJIT: Annotate Symbol#to_s and Symbol#name as returning StringExact
- 10:57 PM Revision 46525fa7 (git): ZJIT: Add return_type to inlined InvokeBuiltin
- 10:57 PM Revision 3fb96ee9 (git): ZJIT: Inline method calls to ISEQs that just do leaf Primitive calls
-
- We treat getinstancevariable differently from other opcodes: it does not
look at the stack for its self operand, but instead looks at
`cfp->self`. In some cases, we might see the `trace_` variant in the
front-end, so make sure we treat t... -
- * ZJIT: Print out full path to --zjit-trace-exits output
This helps with any `chdir`-related issues.
* Don't include dot
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
---------
Co-authored-by: Takashi Kokubun <takashikkbn@... -
-
-
-
-
-
-
-
-
-
-
-
- 07:26 PM Revision 74c3bd77 (git): ZJIT: Remove a duplicated annotation (#14968)
-
- If we send a non-shareable object into a Ractor, it needs to be copied.
```
❯ ruby -W0 -e 'Ractor.new(p(Object.new)) { |o| p(o) }.join'
#<Object:0x00000001240f8cf8>
#<Object:0x00000001240f8870>
```
However we're able to instead... -
- @kddnewton can you mark for backport? Thanks!
-
- Applied in changeset commit:git|0b0da6c4b26f80ad6985722d3fc0f5cdee09125d.
----------
Correctly compile splats in for-loop index in prism
Fixes [Bug #21648]
This is a followup to https://github.com/ruby/ruby/pull/13597.
The added test ... -
- https://github.com/ruby/ruby/pull/14963
-
- ```sh
$ ruby -e "for * in [10]; end"
-e:1: [BUG] Stack consistency error (sp: 15, bp: 14)
ruby 3.4.6 (2025-09-16 revision dbd83256b1) +PRISM [x86_64-linux]
-- Control frame information ----------------------------------------------... -
- Fixes [Bug #21648]
This is a followup to https://github.com/ruby/ruby/pull/13597.
The added test passed but didn't emit the same instructions.
This also handles bare splats and aligns instructions for all cases -
-
- https://github.com/ruby/json/commit/f228b30635
-
- https://github.com/ruby/json/commit/1ba1e9bef9
-
- https://github.com/ruby/stringio/commit/04ba28af00
-
- https://github.com/ruby/rubygems/commit/b2e1810067
-
- https://github.com/ruby/rubygems/commit/687ffd7265
-
- ```
Fetching gem metadata from https://gem.repo4/.
Resolving dependencies...
Resolving dependencies...
# $? => 0
cannot load such file -- diff/lcs
```
https://github.com/ruby/rubygems/commit/668b300261 -
- If we install uri-1.0.4 as default gems. The example may be failed with
version miss-match.
https://github.com/ruby/rubygems/commit/fd2dcb502b -
06:54 AM Revision 1b57e557 (git): [ruby/openssl] test: remove unused small test keys
- Previous commits removed all usages of those small keys.
https://github.com/ruby/openssl/commit/f9d87d7912 -
- Use generic keys whenever possible.
https://github.com/ruby/openssl/commit/73d6a25360 -
- Use generic keys whenever possible.
https://github.com/ruby/openssl/commit/90d6af60b9 -
- Use generic keys whenever possible.
https://github.com/ruby/openssl/commit/cc4d40525c -
- Use generic keys whenever possible.
https://github.com/ruby/openssl/commit/ef4fa5e9b4 -
- Use generic keys whenever possible.
https://github.com/ruby/openssl/commit/689fc271b1 -
- Replace fixed-sized RSA keys with the generic rsa-{1,2,3}.pem keys.
Those test cases do not depend on specific keys or key sizes, and just
need several different keys.
Replace DSA keys with EC keys so that we can run more tests in the F... -
- The EVP_CIPHER_CTX = OpenSSL::Cipher interface for AEAD ciphers is
notoriously complicated and full of pitfalls. I tried to clarify docs
so that users can hopefully connect the Ruby methods with the
corresponding OpenSSL man pages more e... -
-
06:33 AM Revision b839deec (git): [ruby/openssl] Check NULL values for deprecated EVP_PKEY_get0() functions
- In OpenSSL <= 1.1.1, EVP_PKEY_get0() always returned a valid object, so
a NULL check was not necessary. In OpenSSL 3.0, the function can return
NULL (https://docs.openssl.org/3.0/man7/migration_guide/#deprecated-function-mappings),
so gu... -
- https://github.com/ruby/rubygems/commit/9b3a5a8ae9cd
https://github.com/ruby/rubygems/commit/8f6eb4ac64 - 05:51 AM Revision f6d2aef3 (git): [ruby/openssl] Update link to OpenSSL configuration file docs
- https://github.com/ruby/openssl/commit/02ff964114
-
- (https://github.com/ruby/stringio/pull/154)
https://github.com/ruby/stringio/commit/eca2588274 -
- (https://github.com/ruby/stringio/pull/150)
https://github.com/ruby/stringio/commit/ea6e36f797
Co-authored-by: Sutou Kouhei <kou@cozmixng.org> -
- Exclude other git management files too.
https://github.com/ruby/win32-registry/commit/3be0188111 - 03:02 AM Revision 342dfd78 (git): [ruby/resolv] win32/resolv: fix loading of `NV Domain`
- https://github.com/ruby/resolv/commit/da14f1f2fc
-
- ```
TestResolvDNS#test_no_server:
Test::Unit::ProxyError: Timeout::Error
/path/to/ruby/test/resolv/test_dns.rb:531:in 'TestResolvDNS#test_no_server'
``` -
- (https://github.com/ruby/stringio/pull/149)
https://github.com/ruby/stringio/commit/11995db341 -
- (https://github.com/ruby/stringio/pull/152)
https://github.com/ruby/stringio/commit/7ded426718 -
- (https://github.com/ruby/stringio/pull/153)
https://github.com/ruby/stringio/commit/3e9d576441
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
10/26/2025
-
10:59 PM Revision 52ea2220 (git): Fix segfault when moving nested objects between ractors during GC
- Fixes a segmentation fault when moving nested objects between ractors with GC stress enabled and YJIT.
The issue is a timing problem: `move_enter` allocates new object shells but leaves their contents uninitialized until `move_leave` co... -
- Sent a PR to fix this https://github.com/ruby/ruby/pull/14952
-
-
-
-
06:43 PM Bug #21640: Core Pathname is missing 3 methods / is partially-defined
- Longtime rubyist here. I am the author of one of the Pathname PRs that kickstarted this discussion (#64). My PR adds the following methods to Pathname:
``` ruby
# these all use FileUtils
def mkdir_p(...)
def ln(...)
def ln_s(...)
... -
- OK, I've made a PR to document that in https://github.com/ruby/ruby/pull/14953.
But it's just a workaround, it doesn't address any of the problems.
It doesn't address what happens to the pathname gem and the various problems I mentio... -
- * See https://bugs.ruby-lang.org/issues/21640#note-16
- 08:49 AM Revision f53b8194 (git): Stop deleting the reference from superclass when replacing classext.
- Calling the usual rb_iclass_classext_free() causes SEGV because
duplicating a newer classext of iclass had set the reference from superclass
to the newer classext, but calling rb_iclass_classext_free() deletes it. - 08:49 AM Revision 1c81bbf0 (git): free the entry after deleting the reference
- 08:49 AM Revision be118cf9 (git): classext replacement never happen on non-iclass classes
- 08:49 AM Revision efe9a3cd (git): Add several very basic tests to be run with RUBY_NAMESPACE=1 on CI
- To detect breaking namespace features on CI.
-
- (https://github.com/ruby/stringio/pull/151)
https://github.com/ruby/stringio/commit/94bd4a3d87
10/25/2025
-
- I run a git bisect building/testing with these examples (to raise if >2ms avg) and this is the commit that started the issue:
> [be1bbd5b7d40ad863ab35097765d3754726bbd54] M:N thread scheduler for Ractors
Which is the commit the introdu... -
03:31 PM Feature #15381: Let double splat call `to_h` implicitly
- jeremyevans0 (Jeremy Evans) wrote in #note-11:
> […] Maybe in Ruby 4?
Bringing this up since it seems that this year’s Ruby version will be 4.0.
Is this change going to be considered for inclusion in the new release? -
-
- Instead of the offset calculation.
-
- Probably since macOS Runner Image Version 20251020.XXXX, spawned
processes initialize `TMPDIR` environment variable under the hood. -
- And `LD_PRELOAD` is set to `PRELOADENV` on Linux.
-
12:19 PM Revision 377aa2a3 (git): Improve performance of UnicodeNormalize.canonical_ordering_one
- Use array_of_integer.sort! instead of buble-sort-like algorithm
-
- `IS_TYPED_DATA` is no longer a flag in `type`, and the "embedded" flag
has been shifted accordingly.
ruby/ruby#14470 - 09:01 AM Revision 10f0abee (git): Update default gems list at 226caf1a1f3542d9e39e1a72fb43fd [ci skip]
-
- https://github.com/ruby/json/commit/5e61cd7dce
-
- Fix: https://github.com/rails/rails/commit/90616277e3d8fc46c9cf35d6a7470ff1ea0092f7#r168784389
Because the `depth` counter is inside `JSON::State` it can't be used
concurrently, and in case of a circular reference the counter may be
lef... -
04:59 AM Revision 93828c47 (git): merge revision(s) 4368e6c42effc16904e35f753fc2002f0bba375a:
- [PATCH] [ruby/rubygems] Removed credential assertion from stdout
https://github.com/ruby/rubygems/commit/3946be008c -