-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Spammed with textDocument/hover failed + other related errors #14474
Comments
If you provide a reproduction, we can fix the underlying problem. Meanwhile for a workaround you can downgrade to the previous month version. |
Im not entirely sure what is causing it, since its being used in a large project. Some files work fine, but some dont. If i find any clues that would let me make an MVP/repro ill report back. Ill try downgrading further for now |
Check if it reproduces with |
And you can remove parts that are not related to const generics / const eval first. |
I ran into this as well. I'm not able to provide a reproduction as the repo is quite large and proprietary. But it occurred when constructing a class with an async constructor and not calling struct Foo {}
impl Foo {
pub async fn new() -> Self { Foo {} }
}
// error goes away after adding `.await`
let x = Foo::new(); |
I have also observed this and I have minimized my repo to https://github.com/ludios/rust-analyzer-issue-14474-repro. https://github.com/ludios/rust-analyzer-issue-14474-repro/blob/master/src/main.rs With ludiosarchive/rust-analyzer-issue-14474-repro@c6d97b0 (async -> not async), rust-analyzer no longer complains. |
@HKalbasi my reproducer at https://github.com/ludios/rust-analyzer-issue-14474-repro should still be triggering this bug in rust-analyzer 51d5862:
|
Sorry, I was on #14470 which silence (and not fix) this issue. Will look at it. |
My git bisect finds that cd67589 ("beginning of MIR") is the first bad commit. |
rust-analyzer version: v0.3.1459
rustc version: rustc 1.67.0 (fc594f156 2023-01-24)
relevant settings: N/A (i think)
Restarting RA or VSCode, or downgrading to an RA version 1 week older did not work.
Hovering over most parts of my document spams the message in the title, with the following error log:
The text was updated successfully, but these errors were encountered: