summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2025-11-12[ruby/rubygems] Inject assert_ractor if TestGemPackageTarHeaderRactor is ↵Hiroshi SHIBATA
running under the ruby/rubygems repo https://github.com/ruby/rubygems/commit/47f41ce2df
2025-11-12[ruby/rubygems] Added test-unit-ruby-core for assert_ractorHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/be579a9c8c
2025-11-12Fix memory leak in invalidate_ccs_in_iclass_cc_tblPeter Zhu
invalidate_ccs_in_iclass_cc_tbl deletes the ccs from the table but never frees it, causing memory to leak.
2025-11-12[DOC] Tweaks for String#to_rBurdette Lamar
2025-11-12assert_separately: Suppress experimental warningsNobuyoshi Nakada
test-unit depends on power_assert that the recent versions require ruby 3.1 or later. While test-unit rescues syntax error at loading power_assert for old ruby versions, warnings for experimental features are not suppressed, and `assert_separately` fails because stderr is not empty, by default. Since adding `required_ruby_version` to power_assert causes the installation with old rubygems to fail, we just ignore warnings for experimental features totally.
2025-11-12Fix SyntaxError: unexpected keyword_rescue, expecting keyword_end in Ruby ↵Taketo Takashima
2.4 and earlier
2025-11-12Split Ractor tests for Gem::PackageHiroshi SHIBATA
2025-11-12Support multiple require in assert_ractorHiroshi SHIBATA
2025-11-12Reapply "[ruby/rubygems] Fix constants in TAR to be frozen"Hiroshi SHIBATA
This reverts commit 136157e772ab2b2ea08555d0ad821da7dc2bde96.
2025-11-12[Bug #21680] Fix (base**power_of_two).digits(base) bug (#15144)tomoya ishida
Fix wrong condition in base multiplying loop.
2025-11-12Update default gems list at 090099b0c048c655c239a1cb81f551 [ci skip]git
2025-11-12Development of 3.1.9 started.Sutou Kouhei
2025-11-12[ruby/rubygems] maybe this will work?Aaron Patterson
https://github.com/ruby/rubygems/commit/4d8b1c77f4
2025-11-12[ruby/rubygems] add rubygems-generate_index as a dev depAaron Patterson
https://github.com/ruby/rubygems/commit/8df0e4e63e
2025-11-12[ruby/rubygems] Shell out fewer timesAaron Patterson
This is a follow up to #9053. We can avoid shelling out for generating the gem index. https://github.com/ruby/rubygems/commit/e40bafe9f1
2025-11-12Added email and name for `git pull --rebase`Hiroshi SHIBATA
``` Rebasing (1/3) Committer identity unknown *** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. ```
2025-11-12tsort will be extracted at 4.1, not 3.6Hiroshi SHIBATA
2025-11-12Replace Ruby 3.5 with Ruby 4.0Hiroshi SHIBATA
2025-11-12[ruby/error_highlight] Replace Ruby 3.5 with Ruby 4.0Yasuo Honda
This commit updates the Ruby version to follow the commit in Ruby master branch. https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523 https://github.com/ruby/error_highlight/commit/dcecf68d75
2025-11-12[ruby/net-http] Replace Ruby 3.5 with Ruby 4.0Yasuo Honda
This commit updates the Ruby version to follow the commit in Ruby master branch. https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523 https://github.com/ruby/net-http/commit/1e48cfaaf7
2025-11-11Update default gems list at 8afe65cd92ba6a3c64924cad13f24a [ci skip]git
2025-11-11[ruby/io-wait] Bump version to 0.3.5 to incorporate JRuby release fixesCharles Oliver Nutter
https://github.com/ruby/io-wait/commit/284cb654cf
2025-11-11Update default gems list at 5c9d5a66e787b53f422608a9fa2098 [ci skip]git
2025-11-11[ruby/io-wait] 0.3.5.test1 fixing JRuby release processCharles Oliver Nutter
https://github.com/ruby/io-wait/commit/c0ae05e319
2025-11-11Update default gems list at 8428e5e8c62ce24f2cd4d0b27249c1 [ci skip]git
2025-11-11[ruby/io-wait] Bump version to 0.3.4Charles Oliver Nutter
https://github.com/ruby/io-wait/commit/cd163938e5
2025-11-11test_ractor.rb: Delete unnecessary GC.stress fiddlingAlan Wu
assert_ractor() runs in a subprocess.
2025-11-11[ruby/psych] Replace Ruby 3.5 with Ruby 4.0Yasuo Honda
This commit updates the Ruby version to follow the commit in Ruby master branch. https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523 https://github.com/ruby/psych/commit/971b7de078
2025-11-11Don't GC unprotect hash in Coverage.peek_resultPeter Zhu
The call to unprotect the coverages hash was introduced in commit 99093e1 where we used the raw ST table and st_foreach. We now use rb_hash_foreach which no longer requires GC unprotecting the coverages hash.
2025-11-11Update Ruby version to 4.0 for the cgi warnings (#15141)Yasuo Honda
This commit updates the Ruby version in the error message to follow the commit in Ruby master branch. https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523
2025-11-11[ruby/erb] Replace Ruby 3.5 with Ruby 4.0Yasuo Honda
(https://github.com/ruby/erb/pull/94) This commit updates the Ruby version to follow the commit in Ruby master branch. https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523 https://github.com/ruby/erb/commit/a5d42484e4
2025-11-11Remove useless cast in rb_managed_id_table_typePeter Zhu
2025-11-11[ruby/openssl] Replace Ruby 3.5 with Ruby 4.0Yasuo Honda
This commit updates the Ruby version in the error message to follow the commit in Ruby master branch. https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523 https://github.com/ruby/openssl/commit/5a50a4d793
2025-11-11simplify RSRING_GETMEM() definition.nagachika
2025-11-11include/ruby/internal/core/rstring.h: Remove rbimpl_rstring_getmem() definition.nagachika
2025-11-11Remove rbimpl_rstring_getmem() usage as workaround for GCC 15.2.1 ↵nagachika
optimization bug. [Bug #21655]
2025-11-11[Bug #21666] Get rid of use of unspecified valuesNobuyoshi Nakada
2025-11-11Support out-of-place build in ruby/ruby repoHiroshi SHIBATA
2025-11-11Update bundled gems list as of 2025-11-11git
2025-11-10Fix bootstraptest runner driver message (#15072)Randy Stauner
This was a mistake; the code tested for RUBY_PATCHLEVEL but then instead of using it used RUBY_PLATFORM twice.
2025-11-11[ruby/rubygems] Use Spec::Path.relative_gemspecHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/2142e405b0
2025-11-11[ruby/rubygems] build gems directly instead of shelling outAaron Patterson
I'm trying to speed up the bundler tests. The tests shell out a lot in order to build gems. We can build gems without creating a sub-process. This change reduced the test suite time from ~24 minutes, to about ~21 minutes on my machine. Once we have more of these "asset generation" routines done in the same process, I think we can start caching the outputs for further improvements https://github.com/ruby/rubygems/commit/ebf27056c6
2025-11-10ZJIT: Rename things so that they aren't named "not_optimized_optimized" (#15135)Randy Stauner
These refer to "OptimizedMethodType" which is a subcategory of "MethodType::Optimized" so name them after the latter to avoid "not_optimized_optimized".
2025-11-10ZJIT: Set cfp->sp on leaf calls with GC (#15137)Takashi Kokubun
Co-authored-by: Randy Stauner <randy@r4s6.net>
2025-11-10Add test for [Bug #21265]Alan Wu
The crash was fixed by a4dff09be79b52288a47658964d25e5aa84fc960 ("Fix resolving refined module-defined method"). I had a patch for this around for a few months but never merged it. Oops!
2025-11-10Fix printf specificer. %lp doesn't make sense. Triggered -WformatAlan Wu
2025-11-11Revert "ns_subclasses refcount accesses need to be atomic (#15083)" (#15138)Luke Gruber
This reverts commit 2998c8d6b99ec49925ebea42198b29c3e27b34a7. We need to find a better way to fix this bug. Even with this refcount change, errors were still being seen in CI. For now we need to remove this failing test.
2025-11-10[DOC] Clarify `Thread#kill` documentation. (#15132)Luke Gruber
Mention that it is asynchronous and that the killed thread can still run a small amount of ruby code before exiting.
2025-11-10Fix `thread_sched_wait_events` race (#15067)Luke Gruber
This race condition was found when calling `Thread#join` with a timeout inside a ractor. The race is between the polling thread waking up the thread and the `ubf` getting called (`ubf_event_waiting`). The error was that the ubf or polling thread would set the thread as ready, but then the other function would do the same. Fixes [Bug #21614]
2025-11-11ZJIT: Reduce duplication between profiled_type_of_at and resolve_receiver_typeStan Lo