-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Diagnostics are not displayed anymore in Cargoless setup #18847
Comments
The upcoming release should have this fixed (I'll leave this open though until you can confirm). The release is a bit delayed today as we want to fix a pretty bad bug still. |
@Veykril I tried the latest |
Ah apologies I missed the
|
Oh, I see the issue, silly mistake :) |
@Veykril Thanks for taking care of this so quickly! Can confirm it works. |
rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P): v0.3.2237
rustc version: (eg. output of
rustc -V
): nightly/2024-08-23editor or extension: (eg. VSCode, Vim, Emacs, etc. For VSCode users, specify your extension version; for users of other editors, provide the distribution if applicable): Zed 0.167.1 and VSCode 1.96.2
relevant settings: (eg. client settings, or environment variables like
CARGO
,RUSTC
,RUSTUP_HOME
orCARGO_HOME
): Cargoless setup, using Bazel instead.repository link (if public, optional): (eg. rust-analyzer): N/A
description:
Diagnostics are cleared immediately after being generated and displayed (they get cleared so fast that most of the time it's like they were not displayed at all). I tracked the issue down to this commit but I can't tell what's wrong with it. Note that the issue does not occur in a Cargo workspace.
The text was updated successfully, but these errors were encountered: