-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
docs(ref): Highlight commands to answer dep resolution questions #12903
Conversation
Previously, in the rust-lang#6666, the aptly named `cargo lucifer` was suggested for answering resolver questions. Turns out most of these can be answered now, between logging and `cargo tree`. This adds troubleshooting tips to help highlight the use of these commands to answer these questions. Fixes rust-lang#6666
r? @ehuss (rustbot has picked a reviewer for you, use r? to override) |
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.
👍
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.
I wonder if we might want to put all troubleshootings in one place. Maybe under FAQ? It has aleady got some lengthy contents like Why is Cargo rebuilding my code? and What does “version conflict” mean and how to resolve it?
- https://doc.rust-lang.org/nightly/cargo/reference/resolver.html#troubleshooting
- https://doc.rust-lang.org/nightly/cargo/reference/publishing.html#troubleshooting-github-team-access-errors
That said, I do feel this PR fits in the natural reading style.
@@ -517,6 +551,17 @@ But, if you run into this situation, the [`cargo update`] command with the | |||
|
|||
[`cargo update`]: ../commands/cargo-update.md | |||
|
|||
### Why wasn't a newer version selected? |
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.
nit: we can link to an issue having some guidance for debugging as an example. I can't recall any specific one at this moment but I believe there are some.
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.
If you have one, that'd be great. I can't think of ay.
Go ahead and merge this! |
☀️ Test successful - checks-actions |
Update cargo 8 commits in b4d18d4bd3db6d872892f6c87c51a02999b80802..65e297d1ec0dee1a74800efe600b8dc163bcf5db 2023-10-31 18:19:10 +0000 to 2023-11-03 20:56:31 +0000 - fix(cli): Clarify --test is for targets, not test functions (rust-lang/cargo#12915) - Updating "features" documentation to add a note about the new limit on number of features (rust-lang/cargo#12913) - fix: merge `trim-paths` from different profiles (rust-lang/cargo#12908) - Add regression test for issue 6915: features and transitive dev deps (rust-lang/cargo#12907) - chore(deps): update rust crate gix to 0.55.2 (rust-lang/cargo#12906) - chore(deps): update compatible (rust-lang/cargo#12905) - docs(ref): Fix open-semver-range issue link (rust-lang/cargo#12904) - docs(ref): Highlight commands to answer dep resolution questions (rust-lang/cargo#12903) r? ghost
Previously, in the #6666, the aptly named
cargo lucifer
was suggested for answering resolver questions.Turns out most of these can be answered now, between logging and
cargo tree
.This adds troubleshooting tips to help highlight the use of these commands to answer these questions.
Fixes #6666