Skip to content

Comments

[pull] master from ruby:master#97

Merged
pull[bot] merged 30 commits intoturkdevops:masterfrom
ruby:master
Jul 17, 2025
Merged

[pull] master from ruby:master#97
pull[bot] merged 30 commits intoturkdevops:masterfrom
ruby:master

Conversation

@pull
Copy link

@pull pull bot commented Jul 17, 2025

See Commits and Changes for more details.


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

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

tekknolagi and others added 30 commits July 16, 2025 19:17
This helps us rewrite more SendWithoutBlock into SendWithoutBlockDirect.
After several ZJIT fix PRs, the number of failing/crashing tests for
ZJIT has dropped significantly. This removes the unneeded test exclusions.
* YJIT: Side-exit on String#dup when it's not leaf

* Use an enum instead of a macro for bindgen
Fixes `TestZJIT::test_require_rubygems`. It was crashing locally due to
false collection of a live object. See
<https://alanwu.space/post/write-barrier/>.

Co-authored-by: Max Bernstein <max@bernsteinbear.com>
Co-authored-by: Takashi Kokubun <takashi.kokubun@shopify.com>
Co-authored-by: Stan Lo <stan.lo@shopify.com>
This gives a better signal when say you try to run `make zjit-test` on a
YJIT-only build.
This reverts commit 32bfb61, that
requires autoconf 2.70's improved whitespace handling.  It is too
early for some platforms yet.

Fix GH-13910
…precation warning

Like others, it's a remembered option which we are deprecating in favor
of configuration.

ruby/rubygems@801d5dd943
These two specs need the version of Bundler to be faked to pass. In one
of them we're doing it already, and in the other one it will be needed
when bumping the major version of Bundler. So they are no longer truly
realworld anymore.

Realworld specs are hard to maintain, particularly the ones that depend
on the version of Bundler itself, so I'm slowly moving away from them.

I checked the changes that introduced them and I believe it's really
unlikely that any of these catches turns out to be the only spec to
catch a resolver regression. We've completely changed the resolution
engine since and a lot of extra coverage has been added so I believe
it's fine to let these two go.

ruby/rubygems@a363f0168c
I realized `--redownload` is not a good name, because it does not
necessarily redownloads gems. It only forces reinstallation even if gem
is already installed.

So I believe `--force` is actually a better name and the introduction of
`--force` was a misunderstanding of what the `--force` flag did at the
time.

Let's cancel the deprecation of `--force`.

For now the `--redownload` alias is left around until we decide what to
do with it.
Next version for both will be 4.0.0, however, extra work is necessary to
get CI passing against the new major. So for now, I'm bumping just the
minor version.
These branches are only active for 32-bit Windows and Solaris platforms,
codify the fact by changing `#else` to `#elif`'s that explicitly include
those targets and `#error`-out otherwise.
The implementation is only active if `HAVE_STDATOMIC_H` is defined,
and only after the compiler fails to match all currently supported
systems.
@pull pull bot locked and limited conversation to collaborators Jul 17, 2025
@pull pull bot added the ⤵️ pull label Jul 17, 2025
@pull pull bot merged commit 98aa2a6 into turkdevops:master Jul 17, 2025
1 of 2 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.