Skip to content

[pull] master from ruby:master#889

Merged
pull[bot] merged 21 commits intoturkdevops:masterfrom
ruby:master
Mar 27, 2026
Merged

[pull] master from ruby:master#889
pull[bot] merged 21 commits intoturkdevops:masterfrom
ruby:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Mar 27, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

Earlopain and others added 14 commits March 26, 2026 19:15
We still need to do it eagerly when the result will be frozen, same
as for locations.

Fixes the following error for the added test:
> FrozenError: can't modify frozen Prism::ASCIISource: #<Prism::ASCIISource:0x00007ff9d57586f0 @source="1 + 2", @start_line=1, @offsets="\x00\x00\x00\x00">

ruby/prism@0667d23f4f
Previously, key_pad and value_pad were computed from all matching
counters before truncating to the top-N limit, causing excessive
indentation when non-displayed entries had longer names.
The 1-second Timeout.timeout for IO.select waiting on a localhost
empty UDP packet is too tight for loaded CI runners, causing spurious
Timeout::Error failures. Increase to 30 seconds, which is only a
safety net against indefinite hangs.

https://github.com/ruby/ruby/actions/runs/23585200531/job/68676546959
- In #9414 I introduced a fast path to compare gem version.
  The implementation has a couple of caveats such as not computing
  a sort key for gems having more than 4 segments
  (major, minor, patch, security), as well as skipping gems that uses
  a "timestamped" version (such as 0.0.1.ruby/rubygems@202230081030).

  The implementation also had to iterate over the segments couple of
  times.
  There were some concerns from some users that some gems such as
  sorbet (currentlt at version 0.6.13055) would at somepoint reach
  the thresold where we don't compute a sort key
  (any segment > 65_000).

  We can instead use a Mixed-radix solution which is more elegant and
  solve some of those issues (we still don't compute a sort key for
  timestamped version gems as the integer value may be larger than
  what we compute for a gem that has a higher version, such as 0.1.0).

ruby/rubygems@f8e37e6e2d

Co-authored-by: Ufuk Kayserilioglu <ufuk@paralaus.com>
* ZJIT: Compile setblockparam

* ZJIT: Add IntOr HIR and remove MarkBlockParamModified

* ZJIT: Use assert_compiles in codegen tests and tighten IntOr validation

- Use assert_compiles for codegen tests, except for the case that intentionally side exits
- Restrict IntOr validation to CInt64 operands for now

---------

Co-authored-by: Max Bernstein <tekknolagi@gmail.com>
… config` form in specs

ruby/rubygems@bd78b90f64

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…th in-process config helper

ruby/rubygems@85260feefd

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ocess with in-process config helper

ruby/rubygems@f5539440d5

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…rocess with in-process global_config helper

ruby/rubygems@1f97d646b4

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…E"` with in-process config helper

ruby/rubygems@743e4bc9ed

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…lls with in-process config helper

Handle interpolated values, inline calls, and old-style forms that were
missed in previous commits.

ruby/rubygems@d3405c7fe1

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…bundle_config_global

ruby/rubygems@982ad09264

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ctory config

ruby/rubygems@7bf9971ebb

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@pull pull bot locked and limited conversation to collaborators Mar 27, 2026
@pull pull bot added the ⤵️ pull label Mar 27, 2026
dependabot bot and others added 7 commits March 27, 2026 11:31
Bumps the jit group with 1 update in the /zjit directory: [insta](https://github.com/mitsuhiko/insta).


Updates `insta` from 1.46.3 to 1.47.0
- [Release notes](https://github.com/mitsuhiko/insta/releases)
- [Changelog](https://github.com/mitsuhiko/insta/blob/master/CHANGELOG.md)
- [Commits](mitsuhiko/insta@1.46.3...1.47.0)

---
updated-dependencies:
- dependency-name: insta
  dependency-version: 1.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: jit
...

Signed-off-by: dependabot[bot] <support@github.com>
Since #16574, just running zjit-test
causes diffs in Cargo.lock.

This PR gets rid of the diff caused by zjit-test.
Use (void) instead of () for functions taking no parameters.
The previous `cargo update --manifest-path zjit/Cargo.toml` re-resolved
all dependencies, and Rust 1.84+'s MSRV-aware resolver downgraded cc
(1.2.18 -> 1.0.94) and libc (0.2.171 -> 0.2.163) to satisfy yjit's
rust-version = "1.58.0". This caused test_recompile_no_profile_send to
fail on macOS ARM64 CI.

Fix by using `cargo update -p insta` to only update insta and its
transitive deps, preserving the existing cc and libc versions.
On Windows, when a test process is killed after a timeout, the OS may
not release file/directory handles immediately. The Dir.rmdir in the
diagnostic tree-walk raises Errno::EACCES, which was unhandled, causing
the entire cleanup to abort before FileUtils.rm_rf could run.

Rescue EACCES in the best-effort tree cleanup so it falls through to
FileUtils.rm_rf which handles this more robustly.
@pull pull bot merged commit 8b96619 into turkdevops:master Mar 27, 2026
2 of 3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants