-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Lowercase and remove periods in error messages for consistency #8655
Conversation
r? @ehuss (rust_highfive has picked a reviewer for you, use r? to override) |
Will this cause rustc tests to fail? |
I ran: $ fgrep 'Could not document' -r src/test in rust-lang/rust and nothing came up, so I assume that there are no |
It looks like there are a few more error messages that start with an uppercase letter and/or end with a period. |
E.g.: $ grep '"Could not .*"' -r src
src/cargo/util/important_paths.rs: anyhow::bail!("Could not find `{}` in `{}`", file, pwd.display())
src/cargo/util/process_builder.rs: return Err(process_error("Could not set Ctrl-C handler.", None, None).into());
src/cargo/ops/cargo_read_manifest.rs: "Could not find Cargo.toml in `{}`", |
Looks like there are some tests that need to be updated. If you want to update those other error messages, that would be fine, up to you! |
Is there any equivalent of |
What should I do about this message? cargo/src/cargo/core/workspace.rs Lines 155 to 158 in 99134ae
|
It looks like there are a ton of error messages that need to be updated (around 40, by my estimate), so it might not be worth it for now ;) I think I'll stick with only updating the overall "could not document" messages. |
Unfortunately there is not.
The message is probably OK, I believe it is only for library users anyways.
That's totally fine! |
CI should hopefully pass now! |
Okay, all tests are updated and CI is passing! |
Thanks! @bors r+ |
📌 Commit a9424d9 has been approved by |
@bors r+ |
📌 Commit 82c834c has been approved by |
Now it's working! Thanks :) |
Yea, I think the bot was recently restarted, and it sometimes gets confused when that happens. |
bors has been a bit sluggish recently on other things too. |
☀️ Test successful - checks-actions |
Update cargo 8 commits in 126907a7cfccbe93778530e6a6bbaa3adb6c515c..875e0123259b0b6299903fe4aea0a12ecde9324f 2020-08-31 20:42:11 +0000 to 2020-09-08 20:17:21 +0000 - Lowercase and remove periods in error messages for consistency (rust-lang/cargo#8655) - Allow running build-man.sh from any directory (rust-lang/cargo#8682) - docs: add details for cargo check pass where cargo build fail (rust-lang/cargo#8677) - Fix nightly exported_priv_warning test. (rust-lang/cargo#8678) - fix mdbook test with ```ignore/text/sh/console (rust-lang/cargo#8674) - End CACHEDIR.TAG with newline (rust-lang/cargo#8672) - Fixed the fossil repo initialization actually run commands (rust-lang/cargo#8671) - Remove asciidoc attribute in cargo-metadata man page. (rust-lang/cargo#8670)
No description provided.