-
Notifications
You must be signed in to change notification settings - Fork 1.8k
internal: Log flycheck errors #17033
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
Conversation
r? @davidbarsky Not sure if it matters, but we can probably do something like: tracing::error!(%error, formatted_handle, "flycheck failed to run"); |
Yeah, this PR looks good to me (I don't think bors accepts commands from me? I've never tried), but reformat the expression like that is a nice bonus! (It'd be neat if I could figure out how write that transform with SSR.) |
It doesn't (at least not yet), but feel free to approve PRs via github nevertheless!
I don't think SSR can interpolate from strings (changing the {} captures) |
@bors r+ |
☀️ Test successful - checks-actions |
Resolves #16969
The non-cargo messages are appended to the error strings here;
rust-analyzer/crates/flycheck/src/lib.rs
Lines 460 to 482 in 7a8374c
that one is formatted into
Err
here;rust-analyzer/crates/flycheck/src/command.rs
Lines 144 to 155 in 7a8374c
and finally, this PR appends it at the end of existing Flycheck error message