-
Notifications
You must be signed in to change notification settings - Fork 13.3k
x.py says "patch for the non root package will be ignored" #75442
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
Comments
Probably caused by #75427 |
@rust-lang/cargo, is there any way for us to make that warning an error? Ideally this wouldn't pass CI... |
It was done to fix CI in RLS repo and has no effect on Rust. Why should it be a hard error? |
It's worth noting that functionally it doesn't change anything - the I'll update the RLS. I understood that this use case might be useful to support in some way - my intent was to patch the dependency from the crate PoV to emphasize that pulling Rustfmt from git is a temporary measure and a regular crates.io dependency should be used eventually there, rather than trying to globally patch the rustfmt (which is already done by the final Rust virtual manifest). |
It should be a hard error or silenceable -- we shouldn't have warnings on master. |
AFAIK it's hardcoded. I've suggested introduction of The largest implementation complexity I see with the cargo feature is in fact non-cargo lints because rustc prints the source of the lint level, and if cargo sets arguments, rustc would only see those and thus complain about arguments to the users. Maybe initially the feature could only allow It would be great to have this feature for rust-lang/cargo#8437 as well so that one doesn't need to support |
Yeah it's hardcoded to warn: https://github.com/rust-lang/cargo/blob/7bce509826e29bd79566f7a33621fea7e7a657f9/src/cargo/core/workspace.rs#L828 |
@Xanewok, any news on updating RLS? I can take care of removing the patch and bumping the submodule to a separate branch on rust-lang/rls if you'd like (the patch shouldn't be needed for rust-lang/rust, but I guess is needed upstream). |
You don't need a separate branch. You only have to create a different Cargo.toml file and then change ci to do sth like |
I guess that would work too, but personally that seems somewhat more complicated and more likely to lead to problems of only updating one of them. |
x.py
recently started saying something like this several times on almost every invocation:The text was updated successfully, but these errors were encountered: