This notification keeps appearing and it's very distracting. I have already enabled the VSCode "Do Not Disturb" mode, but the notification keeps showing up. I would like to know how to disable it.
Do we have something like this?
"rust-analyzer.notifications.cargoCheck": false
Did you check Rust Analyzer's issue tracker?
Searching for "Notifications" shows this ticket as the top result:
opened 12:41AM - 23 Feb 23 UTC
C-feature
Feature request: Add an option to suppress all Rust Analyzer errors from bubblin… g up to VSCode toasts.
---
Each and every single Rust Analyzer crash results in a toast being displayed in VSCode. Even if you chose to ignore the toast and leave it up, repeat toasts will play an attention-grabbing animation. I love Rust, I love Rust Analyzer, I'm immensely grateful to everyone in the world that made those two possible, but the toasts are like a splinter I just can't ignore. Maybe it's some type of OCD, but it's really painful 🙏 I brought this up in [issue 717](https://github.com/rust-lang/rust-analyzer/issues/717) as well.
## "We should fix the bugs instead"
I get a deluge of popups when I'm trying to `git rebase`. As I would fully expect, git merge conflicts aren't valid Rust and I don't expect (or want) Rust Analyzer to understand them. There are an infinite number of edge cases that fit this description. Process was killed, container was closed, SSH terminated, filesystem is FUBAR... it's impossible to fix every bug. Making the server hardened against crashes is one option (IMO probably not a great option, panics are a good way to report stack traces and handle truly unrecoverable situations 'cleanly'). I don't think fixing every bug is a good substitution for hiding these toasts.
## "We need bug reports"
Microsoft has a [guide on user telemetry](https://code.visualstudio.com/api/extension-guides/telemetry) for VSCode. A few hundred people opted into telemetry is orders of magnitude more useful than hoping someone opens an issue for each of the many error toasts that popup throughout the day, many of which aren't useful because the user knows exactly why the Rust isn't valid. This kind of stuff is largely plug-and-play too, things like Sentry.io can help you filter out non-errors (like trying to parse a git merge conflict).
