Repository navigation
Conversation
rustix 1.1.5 marks unwritten bytes as initialized when an xattr function gets a zero-length buffer. It is reached through crossterm, tempfile and tar's xattr, and cargo audit --deny warnings fails on the advisory.
--version always checks for a newer release online, unlike the background check that CHCTL_UPDATE_CHECK_TIMEOUT_MS turns off. Since v0.5.1 was published, main (0.5.0) prints an update notice on stderr and the assertion that stderr stays empty fails on every PR. The test is about CLI output under a closed reader, which local output and --help still cover.
balanza
temporarily deployed
to
cloud-integration
November 13, 2026 06:37 — with
GitHub Actions
Inactive
GitHub no longer provisions macos-14 runners: the job fails at once with "The configuration 'macos-14-arm64-us-default' is not supported". macos-15 still covers the macOS arm64 install.
Member
|
Thanks; already fixed in another PR pending merge. Will close this as duplicate. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes 1440
Two failures that hit every PR right now (seen on #1439), neither caused by the PR's own changes:
cargo audit:cargo update -p rustix(1.1.5 → 1.1.6, lockfile only). rustix is reached through crossterm, tempfile and tar's xattr.local_stdout_test:--versionalways checks for a newer release online, whichCHCTL_UPDATE_CHECK_TIMEOUT_MSdoes not turn off. Since v0.5.1 was published, the 0.5.0 build prints an update notice on stderr, so the empty-stderr assertion fails. The fix drops--versionfrom that test. Local output and--helpstill cover the closed-stdout behaviour, and the production code is unchanged.Install Test (macos-14): GitHub no longer provisions themacos-14runner, so the job fails at once. The fix drops it from the install matrix;macos-15still covers macOS on arm64.Checks: fmt, both clippy configurations and
cargo audit --deny warningsare clean, andlocal_stdout_testpasses.Note
Low Risk
Lockfile security bump and test/CI matrix tweaks only; no production behavior changes.
Overview
Addresses failing cargo audit and local_stdout_test by updating the lockfile and tightening the hermetic CLI test, and narrows install CI to supported runners.
rustix is bumped 1.1.5 → 1.1.6 in
Cargo.lock(RUSTSEC-2026-0486), with related dependency edges shifting towindows-sys 0.52.0. The closed-stdout integration test no longer exercises--version—it can emit an update notice on stderr because the online update check isn’t fully disabled—while local list and --help still validate quiet behavior.Install workflow matrix drops macos-14, leaving ubuntu-22.04, ubuntu-24.04, and macos-15.
Reviewed by Cursor Bugbot for commit f4bb93a. Bugbot is set up for automated code reviews on this repo. Configure here.