Skip to content

Conversation

epage
Copy link
Contributor

@epage epage commented Oct 1, 2025

No description provided.

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Oct 1, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 1, 2025

r? @weihanglo

rustbot has assigned @weihanglo.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Copy link
Member

@weihanglo weihanglo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@epage do you have link to every changelog that renovatebot fetched for us?

I usually walk through that to ensure everything is good.

checksum = "884e2677b40cc8c339eaefcb701c32ef1fd2493d71118dc0ca4b6a736c93bd67"

[[package]]
name = "libc"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rustix@1.1.1+ seems to have the fixed it, we should be good to go: https://diff.rs/rustix/1.0.8/rustix/1.1.1/src%2Fbackend%2Flibc%2Fc.rs

Do you want to also unpin libc? #15919

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep this change uncontroversial and do that in a dedicated commit/PR for easier auditing, bisecting, and reverting.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@epage
Copy link
Contributor Author

epage commented Oct 2, 2025

do you have link to every changelog that renovatebot fetched for us?

Most of this is from #16028

@weihanglo weihanglo added this pull request to the merge queue Oct 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 3, 2025
@weihanglo
Copy link
Member

Huh, weird. The first time seeing this: https://github.com/rust-lang/cargo/actions/runs/18209522651/job/51847233913#step:15:4766

thread 'publish::invalid_token' (1268) panicked at tests\testsuite\publish.rs:3619:10:

---- expected: tests\testsuite\publish.rs:3606:27
++++ actual:   stderr
   1    1 | [UPDATING] crates.io index
   2      - [PACKAGING] foo v0.0.1 ([ROOT]/foo)
   3      - [PACKAGED] 4 files, [FILE_SIZE]B ([FILE_SIZE]B compressed)
   4      - [UPLOADING] foo v0.0.1 ([ROOT]/foo)
   5      - [ERROR] failed to publish foo v0.0.1 to registry at http://127.0.0.1:[..]/
        2 + [WARNING] spurious network error (3 tries remaining): [28] Timeout was reached (Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds)
        3 + [WARNING] spurious network error (2 tries remaining): [56] Failure when receiving data from the peer (Recv failure: Connection was reset)
        4 + [WARNING] spurious network error (1 try remaining): [7] Could not connect to server (Failed to connect to 127.0.0.1 port 58734 after 2027 ms: Could not connect to server)
        5 + [ERROR] download of config.json failed
        6 + 
        7 + Caused by:
        8 +   failed to download from `[http://127.0.0.1:58734/index/config.json`](http://127.0.0.1:58734/index/config.json%60)
   6    9 | 
   7   10 | Caused by:
   8      -   token contains invalid characters.
   9      -   Only printable ISO-8859-1 characters are allowed as it is sent in a HTTPS header.
       11 +   [7] Could not connect to server (Failed to connect to 127.0.0.1 port 58734 after 2026 ms: Could not connect to server)

Requeing

@weihanglo weihanglo added this pull request to the merge queue Oct 3, 2025
Merged via the queue into rust-lang:master with commit 94f6379 Oct 3, 2025
27 checks passed
@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Oct 3, 2025
@epage epage deleted the update branch October 3, 2025 15:02
bors added a commit to rust-lang/rust that referenced this pull request Oct 3, 2025
Update cargo submodule

24 commits in f2932725b045d361ff5f18ba02b1409dd1f44e71..2394ea6cea8b26d717aa67eb1663a2dbf2d26078
2025-09-24 11:31:26 +0000 to 2025-10-03 14:13:01 +0000
- Recommend `package.rust-version` in the Rust version section of `reference/semver.md`. (rust-lang/cargo#15806)
- fix(toml): Prevent non-script fields in Cargo scripts (rust-lang/cargo#16026)
- chore(ci): unpin libc (rust-lang/cargo#16044)
- chore: Update dependencies (rust-lang/cargo#16034)
- Fix FileLock path tracking after rename in package operation (rust-lang/cargo#16036)
- Lockfile schemas error cleanup (rust-lang/cargo#16039)
- Convert a multi-part diagnostic to a report (rust-lang/cargo#16035)
- fix(run): Override arg0 for cargo scripts  (rust-lang/cargo#16027)
- Public in private manifest errors (rust-lang/cargo#16002)
- chore(deps): update actions/checkout action to v5 (rust-lang/cargo#16031)
- fix: remove FIXME comment that's no longer a problem (rust-lang/cargo#16025)
- Add retry for `git fetch` failures in `CARGO_NET_GIT_FETCH_WITH_CLI` path (rust-lang/cargo#16016)
- Added better filesystem layout testing harness (rust-lang/cargo#15874)
- Small cleanup to normalize_dependencies (rust-lang/cargo#16022)
- fix: better error message for rust version incompatibility (rust-lang/cargo#16021)
- fix(shell): Use a distinct style for transient status (rust-lang/cargo#16019)
- chore(deps): Depend on `serde_core` in `cargo-platform` (rust-lang/cargo#15992)
- Remove package-workspace from unstable doc index (rust-lang/cargo#16014)
- fix(shell): Switch to annotate snippets for notes (rust-lang/cargo#15945)
- docs: update changelog (rust-lang/cargo#15986)
- chore(ci): add rustfmt for docs job (rust-lang/cargo#16013)
- chore: bump to 0.93.0 (rust-lang/cargo#16009)
- fix(config): combine key error context into one (rust-lang/cargo#16004)
- test(docker): openssh requires a newer libcrypto3 (rust-lang/cargo#16010)

r? ghost
@rustbot rustbot added this to the 1.92.0 milestone Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants