[pull] master from ruby:master#902
Merged
pull[bot] merged 21 commits intoturkdevops:masterfrom Apr 1, 2026
Merged
Conversation
The curl requests to stdgems.org occasionally fail with connection errors, causing spurious CI failures. Add curl's built-in retry flags to handle transient network issues with exponential backoff. example: https://github.com/ruby/ruby/actions/runs/23825769292/job/69448266927
Bumps the github-actions group with 1 update in the / directory: [taiki-e/install-action](https://github.com/taiki-e/install-action). Updates `taiki-e/install-action` from 2.70.3 to 2.70.4 - [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@6ef672e...bfadeab) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.70.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
This function prevents other users from opening this device for writing so not to be sent messages using commands such as `talk` or `wall`.
[Feature #21861]
ruby/rubygems@6cd04a57da Co-authored-by: hsbt <12301+hsbt@users.noreply.github.com>
…tions ruby/rubygems@7ebc1abafd Co-authored-by: hsbt <12301+hsbt@users.noreply.github.com>
…p after use ruby/rubygems@498401c010 Co-authored-by: hsbt <12301+hsbt@users.noreply.github.com>
…tform and host The send_push_request method previously skipped all attestation handling on JRuby, non-rubygems.org hosts, or outside GitHub Actions. This meant that even when a user explicitly passed --attestation with a local sigstore bundle, the attestation was silently ignored. Now we check options[:attestations] first and always use them when provided, only gating the auto-attestation path behind the platform/host/CI checks. ruby/rubygems@0178a0dc56 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… verbose When auto-attestation fails, the warning previously included e.full_message with a full backtrace that could be noisy and expose local paths. Now only e.message is shown by default, and the full backtrace is included only when Gem.configuration.really_verbose is set. ruby/rubygems@4a4d9b8911 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The method compared against a hardcoded string, so a trailing slash (e.g. "https://rubygems.org/") would cause auto-attestation to be silently skipped. Now we chomp the trailing slash and compare against Gem::DEFAULT_HOST to be consistent with the rest of the codebase. ruby/rubygems@a4fa24c8cf Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…of pinning version Hardcoding sigstore-cli:0.2.2 meant rubygems would need a new release whenever sigstore-cli ships a new version. Using --conservative lets gem exec prefer an already-installed version and falls back to the latest when sigstore-cli is not yet installed. ruby/rubygems@6ac00f34de Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
[Bug #21818] Currently exceptions can be sent across ractors, but because of a limitation in the TypedData API, the exception backtrace is duped as an empty backtrace. The problem is that backtraces are embedded objects, hence the classic `rb_class_alloc(klass)` API is insufficient because we need to know the size of the Backtrace object we're duping to instantiate the copy. This is worked around by changing Ractors to call `#clone` on objects rather than use `rb_obj_clone`, and to implement `Thread::Backtrace#clone` to properly clone the variable size object.
I've been seeing this for a while now:
```
../../../../ext/prism/../../src/memchr.c: In function ‘pm_memchr’:
../../../../ext/prism/../../src/memchr.c:35:16: warning: return discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
35 | return memchr(memory, character, number);
| ^~~~~~
```
ruby/prism@a3b1f10dbc
- Avoid unnecessarily binding sender sockets, as ephemeral ports can very occasionally conflict on Linux. This investigation is assisted by Claude Code. - Compare timestamps using a range instead of relying on `inspect`. - Use the `timestamp_retry_rw` helper in `test_bintime` as well. - Use `String#unpack1` with offset to extract the timestamp data. Co-authored-by: Koichi Sasada <ko1@atdot.net>
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.
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 : )