-
Notifications
You must be signed in to change notification settings - Fork 902
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
cargo fmt --all completely stops formatting when failing on a single file #3008
Comments
It seems to me that in the latter case rustfmt is not using the expected rustfmt.toml. Could you please try without rustfmt.toml and see if those two still format differently? |
|
For the record, I also get the different formatting behavior between |
I tried to understand how It seems that
|
When formatting |
I have the same issue using: https://github.com/otavio/updatehub It fails with 101 exit status. Running it on all files does format them but using |
I found that the option which, in our case, triggers the issue is the |
@otavio checking what's wrong with your example, looks like it is the code block. |
Do you mean the diagram? |
yes |
But why it would abort rustfmt? and more important ... silently? |
I reported #3055 with a small test case for the issue. |
I'd like to mention that as #3055 has been fixed, this does not happen to me anymore. However, this issue seems to be a general issue which It would be good if it at least prints something on the stderr so the user knows it is stopping the formatting without completing. |
This is a very old issue, but I started seeing this problem in tests folders (when using a |
Is there a way around this yet? I have a very long and descriptive name like |
Can anyone provide a link to a repo where this still happens? |
meta:
rustc 1.30.0-nightly (2d4e34ca8 2018-09-09)
cargo fmt --version
:rustfmt 0.99.4-nightly (1c40881 2018-08-27)
rustfmt --version
:rustfmt 0.99.4-nightly (1c40881 2018-08-27)
example crate: clippy
changed files:
changed files:
What is going on here?
The text was updated successfully, but these errors were encountered: