-
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
Request textDocument/*
failed
#13006
Comments
Has been happening constantly for maybe 2 weeks now? I even get it on other machines in every crate I work on. |
It happens since I work with multiple crates. |
There's already some known chalk bugs resulting in this, but we'll need some sample code that shows the problem. |
It's a bug in the chalk crate, which we use for trait solving. It gets into an infinite loop. #12897 is one example. Code using the RustCrypto ( You can try reducing |
is it possible to demote these errors from "popup" to "log only"? They are pretty irritating and not user actionable anyway |
I agree with above, and I would happily enable any kind of telemetry if it would aid with fixing these. They happen all the time for me. |
This also happens on brand new project created via cargo (using vscode with rust-analyzer):
|
That panic (should be) fixed on master (so by next monday). AS for the original panic posted here, given its a chalk panic I'll close this as there isnt too much for us to do there right now |
I always getting following language server error notifications for the
rust-analyzer
.Request textDocument/semanticTokens/range failed.
Request textDocument/inlayHint failed.
Request textDocument/semanticTokens/full failed.
The Output debug print is the following.
I use the lastest
rust-analyzer
extension from VSCode.I didn't installed the binary with homebrew.
What can I do to prevent that
rust-analyzer
spamms that error notifications?The text was updated successfully, but these errors were encountered: