[pull] master from ruby:master - #1411
Merged
Merged
Conversation
It is not used outside of file.c.
Bumps the github-actions group with 2 updates in the / directory: [necojackarc/auto-request-review](https://github.com/necojackarc/auto-request-review) and [taiki-e/install-action](https://github.com/taiki-e/install-action). Updates `necojackarc/auto-request-review` from 035f049cb68460341ab744f19aa9f31aae685e36 to 9a4b11888f2d60c79120c5413f13eb63febc2b68 - [Release notes](https://github.com/necojackarc/auto-request-review/releases) - [Commits](necojackarc/auto-request-review@035f049...9a4b118) Updates `taiki-e/install-action` from 2.87.11 to 2.87.12 - [Release notes](https://github.com/taiki-e/install-action/releases) - [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md) - [Commits](taiki-e/install-action@9534c84...3f74d7c) --- updated-dependencies: - dependency-name: necojackarc/auto-request-review dependency-version: 9a4b11888f2d60c79120c5413f13eb63febc2b68 dependency-type: direct:production dependency-group: github-actions - dependency-name: taiki-e/install-action dependency-version: 2.87.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
…ubprocess output Under RUBY_BOX=1 every spawned ruby prints an experimental warning to stderr, which breaks assertions on subprocess output in both suites. The Bundler specs filter the captured stderr instead of adding -W:no-experimental to RUBYOPT, because several of them assert the exact RUBYOPT propagated to subprocesses. ruby/rubygems@72b2e47376 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ruby::Box leaves $? uninitialized, so status checks read success after a failing command. Under RUBY_BOX=1 this made Gem::Source::Git#rev_parse swallow rev-parse failures and the release tool carry on with empty output. https://bugs.ruby-lang.org/issues/22280 ruby/rubygems@67147d48a1 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Each box gets detached copies of the stdio globals, so reassigning $stdout or $stderr cannot capture output written by Kernel#warn, Kernel#puts or subprocesses. https://bugs.ruby-lang.org/issues/21867 ruby/rubygems@ec8b8db347 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ruby::Box ignores $VERBOSE=, so assert_ractor cannot keep the Ractor experimental warning out of the child stderr. https://bugs.ruby-lang.org/issues/22282 ruby/rubygems@90bdecc0dc Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A command line or RUBYOPT -r bypasses the RubyGems Kernel#require override under RUBY_BOX=1, so the gem is never activated. The cargo tests require inside -e instead, and the BUNDLE_CLEAN native extension example, which needs RUBYOPT -r, is skipped. https://bugs.ruby-lang.org/issues/22295 ruby/rubygems@430ec00de6 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A blanket stub also caught the path lookups of a lazy require of rubygems/yaml_serializer, which crashed with Errno::ENOENT under RUBY_BOX=1 with the parallel workers. These examples only need bundler/setup faked. ruby/rubygems@ca3a38f603 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…process The recursion is not in RbConfig.expand. Inside a box defined?($gvar) does not see assignments made in that box, so mkmf have_devel? never sees its own memo. https://bugs.ruby-lang.org/issues/22283 ruby/rubygems@c0d86f6436 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ase Ruby Content-addressed gems pin required_ruby_version to ~> X.Y.0, which a prerelease Ruby such as 4.1.0.dev does not satisfy, so the gem is never resolved on ruby-head. ruby/rubygems@f780cbd764 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The publish workflow posted nothing, so its result could only be found on the Actions page. The version is taken from the event instead of RUBY_VERSION so that a failure before that step still names the version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Only test_mode_settings itself was checked to be a Hash, and its delay and error values were passed to rb_hash_aref as they were. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
server_thread.value waited for an accept that never returned once TCPSocket.new had raised, hiding the failure behind a hang. Use stop_accept_thread as the newer tests do. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
It only fills in the given hints and allocates nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 : )