Tracing report annoying type mismatch but rust compiles no error

[guoqingbao]

Bug Report

The latest tracing library report annoying type mismatch under rust analyzer

expected &'static (dyn Callsite + 'static), found &DefaultCallsiterust-analyzer[E0308](https://doc.rust-lang.org/stable/error_codes/E0308.html)
expected &'static [&'static str], found &[&'static str; 1]rust-analyzer[E0308](https://doc.rust-lang.org/stable/error_codes/E0308.html)

Simple usage

    tracing::info!(
        "KvCache Transfer: Seq {} prefill finished and received in {} ms!",
        seq.id,
        transfer_duration
   );

There is no duplicate tracing in my workspace

cargo tree -d | grep tracing
├── tracing-attributes v0.1.31 (proc-macro)
│ └── tracing v0.1.44
│ ├── tracing-subscriber v0.3.22

Version

tracing = "0.1.44"
tracing-subscriber = { version = "0.3.22", features = ["env-filter"] }

Platform

Ubuntu 22.04

Rust analyzer: Version 0.4.2741

[nestyy1337]

Hi, I've triggered this when I forgot to add rust-src path to my project's nix-shell. It happens after rust-analyzer tries to find relevant source file producing such error:

ERROR flycheck 0: File with cargo diagnostic not found in VFS: file not found: /build/rustc-1.92.0-src/library/core/src/pin.rs

I'm running rust 1.92.0 with rust-analyzer 0.3.2753

[mladedav]

If rustc compiles the code then this is a bug in rust-analyzer. You might want to open an issue there if there isn't and link it here.

If the errors are sufficiently annoying, you might want to use the rust-analyzer.diagnostics.disabled option to skip its checks for E308. Any actual errors will still be caught when rust analyzer invokes cargo check or cargo clippy, whatever you have configured, though you might get the feedback slower for larger projects.