-
Notifications
You must be signed in to change notification settings - Fork 14k
Weekly cargo update + update allowed dependencies list
#145849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
rustbot has assigned @Mark-Simulacrum. Use |
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. These commits modify the If this was unintentional then you should revert the changes before this PR is merged. The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging. |
This comment has been minimized.
This comment has been minimized.
|
Error looks spurious, restarting the job to check. |
|
Need to rebase, lock file was changed. |
Ok, I canceled the rerun job then, no need to waste CPU cycles if it will run again anyway. |
2473f30 to
f3ef87e
Compare
This comment has been minimized.
This comment has been minimized.
|
@rustbot blocked (#145858 (comment)) |
|
☔ The latest upstream changes (presumably #145871) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@clubby789 #145858 is merged, you may rebase |
|
Reminder, once the PR becomes ready for a review, use |
f3ef87e to
300b3f7
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Oh, yes, stringdex is tested to recover perf in #145911, so shouldn't be bumped. |
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors r+ p=1 |
Weekly `cargo update` + update allowed dependencies list Fixes #145516
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
|
@rustbot author It probably makes sense to split this up into smaller chunks to make it easier to make incremental progress. |
|
Sounds good. I believe this issue is in |
| "windows_x86_64_gnullvm", | ||
| "windows_x86_64_msvc", | ||
| "wit-bindgen-rt@0.39.0", // pinned to a specific version due to using a binary blob: <https://github.com/rust-lang/rust/pull/136395#issuecomment-2692769062> | ||
| "wit-bindgen@0.46.0", // pinned to a specific version due to using a binary blob: <https://github.com/rust-lang/rust/pull/136395#issuecomment-2692769062> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wit-bindgen@0.46.0 contains a binary blob. It seems like we accidentally already got a dependency on this blob for the standard library again though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @alexcrichton this was added to the standard library in #145944
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes the binary blob there is expected, and I'm happy to provide context for it if necessary. (unsure if you were looking for any other sort of particular feedback here)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding is that we intended to pin wit-bindgen-rt to a version from before the binary blob was introduced because some distros don't like binary blobs in source tarballs. I assume the reason you are using a binary blob is because of weak symbols. Would something like the binary blobs into a separate crate and then replacing this crate on the rustc side with [patch.crates-io] with a pure rust implementation that uses the unstable #[linkage = "weak"] or something like that work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right yeah the blobs are just for weak symbols. Personally if it comes down to [patch] what I'd personally prefer is to not support building WASI targets for distros. For example remove all of the blobs from the vendored source tarball and then have the WASI target just fail to build. Basically I personally don't want to sink too much effort into fixing this myself, so I'd try to play the game of "what's the lowest effort fix that satisfies everyone", and AFAIK there aren't users wanting to build wasi targets from distros.
…-11-25, r=ehuss Update rustbook dependencies rust-lang#145849 (comment)
…-11-25, r=ehuss Update rustbook dependencies rust-lang#145849 (comment)
…-11-25, r=ehuss Update rustbook dependencies rust-lang#145849 (comment)
Rollup merge of #148833 - clubby789:cargo-update-rustbook-11-11-25, r=ehuss Update rustbook dependencies #145849 (comment)
…=ehuss Update rustbook dependencies rust-lang/rust#145849 (comment)
…11-25, r=Mark-Simulacrum Bump library dependencies rust-lang#145849 (comment)
…rk-Simulacrum Bump library dependencies #145849 (comment)
…11-25, r=Mark-Simulacrum Bump library dependencies rust-lang#145849 (comment)
Rollup merge of #148832 - clubby789:cargo-update-library-11-11-25, r=Mark-Simulacrum Bump library dependencies #145849 (comment)
Fixes #145516