Skip to content
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

feat: emit error if package not found within workspace #15071

Merged
merged 2 commits into from
Feb 6, 2025

Conversation

linyihai
Copy link
Contributor

@linyihai linyihai commented Jan 16, 2025

What does this PR try to resolve?

Fixes #12978

currently, if --package and --workspace passe in the same time, the --package will be ignore even the package doesnt exist in the workspace, this PR regards this behavior as an error

How should we test and review this PR?

one commit add test, one commit fixes the issue.

Additional information

@rustbot
Copy link
Collaborator

rustbot commented Jan 16, 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

@rustbot rustbot added A-cli Area: Command-line interface, option parsing, etc. Command-add Command-package Command-publish Command-remove Command-tree S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 16, 2025
@linyihai linyihai marked this pull request as draft January 17, 2025 07:22
@linyihai linyihai marked this pull request as ready for review January 17, 2025 08:45
@linyihai linyihai changed the title feat: warning --package will be ignore if --workspace presents feat: emit error if package not found within workspace Feb 6, 2025
Copy link
Contributor

@epage epage left a comment

Choose a reason for hiding this comment

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

Thanks!

While this turns a success case into an error case, I'm going to go ahead and merge this without an FCP because this was discussed in a Cargo team meeting where we had consensus. This was a bug that we are fixing which limits how much focus we put on compatibility. We are going straight to an error as we feel there is little value gained from a more gradual transition in this case.

If someone does have some concerns, we have nightly and beta to address them.

@epage epage added this pull request to the merge queue Feb 6, 2025
Merged via the queue into rust-lang:master with commit 027b415 Feb 6, 2025
21 checks passed
@linyihai linyihai deleted the workspace-warn branch February 6, 2025 08:47
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 8, 2025
Update cargo

14 commits in 0e3d73849ab8cbbab3ec5c65cbd555586cb21339..2928e32734b04925ee51e1ae88bea9a83d2fd451
2025-02-01 20:14:40 +0000 to 2025-02-07 16:50:22 +0000
- Simplify backtrack (rust-lang/cargo#15150)
- Don't use on Solaris libc::LOCK_* which were removed from libc in ver… (rust-lang/cargo#15143)
- feat: emit error if package not found within workspace (rust-lang/cargo#15071)
- Make cache tracking resilient to unexpected files (rust-lang/cargo#15147)
- Small resolver cleanups (rust-lang/cargo#15040)
- feat: add `cargo pkgid` support for cargo-script (rust-lang/cargo#14961)
- Suggest similar feature names on CLI (rust-lang/cargo#15133)
- fix: Don't use "did you mean" in errors (rust-lang/cargo#15138)
- Fix changelog link (rust-lang/cargo#15142)
- chore(deps): update rust crate rand to 0.9.0 (rust-lang/cargo#15129)
- Remove the original changelog (rust-lang/cargo#15123)
- chore(deps): update rust crate gix to 0.70.0 (rust-lang/cargo#15128)
- allow windows reserved names in CI (rust-lang/cargo#15135)
- removed a word that was repeated (rust-lang/cargo#15136)
@rustbot rustbot added this to the 1.86.0 milestone Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-cli Area: Command-line interface, option parsing, etc. Command-add Command-metadata Command-package Command-publish Command-remove Command-tree S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

With package selection, --package <non-existent> --workspace doesn't warn or error
4 participants