Rust-analyzer showing persistent phantom diagnostics after upgrading to Rust 1.93.1 in a workspace project
โ Rust ๐ 2026-02-14 ๐ค surdeus ๐๏ธ 1Hello,
Iโm encountering an issue after upgrading from Rust 1.93 to Rust 1.93.1, and I would appreciate any insight from the community.
Iโm working on a Rust workspace composed of multiple sub-crates. Everything was functioning correctly with Rust 1.93 and VSCodium (VSCode). However, since upgrading to Rust 1.93.1, Iโm seeing more than 50 warnings of the following type every time I open the IDE:
2026-02-14T18:56:47.153796764+01:00 WARN Ignoring package label Cargo { package_id: PackageId { repr: "path+file:///home/xxxxxxxxx/project_xxx#0.1.0" } } and applying diagnostics to the whole workspace
[...]
[...]
2026-02-14T18:56:47.153796791+01:00 WARN Ignoring package label Cargo { package_id: PackageId { repr: "path+file:///home/xxxxxxxxx/project_xxx#0.1.0" } } and applying diagnostics to the whole workspace
[...]
[...]
2026-02-14T18:56:51.863376819+01:00 WARN overly long loop turn took 139.992406ms (event handling took 139.944731ms): PrimeCaches(End { cancelled: false })
[...]
[...]
In addition, Iโm experiencing persistent โghostโ errors in the source code. Even after fixing the reported issue, rust-analyzer continues to display the error. The only way to clear it is to manually restart rust-analyzer, and this needs to be done repeatedly after each modification.
So far, I have tried:
cargo clean- Removing
Cargo.lock - Deleting the
/targetdirectory entirely
Unfortunately, none of these actions resolved the problem.
Has anyone experienced similar behavior after upgrading to Rust 1.93.1, particularly in a workspace setup? Any guidance or suggestions would be greatly appreciated.
Thank you in advance.
6 posts - 3 participants
๐ท๏ธ Rust_feed