[VSCode] Request textDocument/semanticTokens/full failed.

[owen-hope]

Just updated my vscode to the August 1.49v and now I am getting this error show up every time I open a file or try to type in one:

[ERROR rust_analyzer::dispatch] unknown request: Request { id: RequestId(U64(71)), method: "textDocument/semanticTokens/full", params: Object({"textDocument": Object({"uri": String("file:///Users/ohope/develop/fresnel/fresnel-code/trace/packet-handling-rust-logic/src/parasitic_trace.rs")})}) } [Error - 8:18:37 AM] Request textDocument/semanticTokens/full failed. Message: unknown request Code: -32601

This is on a mac.

[lnicola]

That's a mismatch between the Code extension and the LSP binary. Did you build rust-analyzer from source? You might have an older version floating around.

[owen-hope]

@lnicola Nope, I downloaded the extension right from vscode.

[guzongmin]

Same issue

[shenshouer]

Same issue

[hammypants]

Mine is not failing on Windows, but with Sept 14th nightly it has gotten to be extremely slow. On the order of 5-15s per request for semanticTokens/full and codeAction.

I should note it did not do this on nightly of Sept 13.

In my case I got to try this on an older VSCode setup and it still is still very slow, so I opened a diff issue.

[kjeremy]

@owen-hope Can you post the extension and server version numbers? You say you have the latest version of rust-analyzer extension but do you have the latest server binary?

[fuyumatsuri]

I'm seeing the same thing on windows with current version of the extension (0.2.313, stable channel) and the server binary that was auto downloaded/included.

~\AppData\Roaming\Code\User\globalStorage\matklad.rust-analyzer 
> .\rust-analyzer-windows.exe --version
rust-analyzer ac4b134

[kjeremy]

ac4b134 is the 2020-08-30 release of the rust-analyzer binary. The semantic tokens change for both client and server was merged in after that in #5930.

[fuyumatsuri]

It seems in my case, state.serverVersion was somehow set to 0.2.313 even though the server binary wasn't actually updated. I forced the extension to download an updated version anyways, and that has fixed it for me.

I'm not really sure how I got in this state, but one "suspicious" thing might be that before updating my vscode from last weeks version, I installed WSL and installed the vs code extension in it. Using the extension under WSL does seem to have a separate globalState than using it under the host windows, so that shouldnt be the cause, but you never know.

[kjeremy]

I think WSL has to be updated separately.

…

On Wed, Sep 16, 2020, 7:58 PM fuyu ***@***.***> wrote: It seems in my case, state.serverVersion was somehow set to 0.2.313 even though the server binary wasn't actually updated. I forced the extension to download an updated version anyways, and that has fixed it for me. I'm not really sure how I got in this state, but one "suspicious" thing might be that before updating my vscode from last weeks version, I installed WSL and installed the vs code extension in it. Using the extension under WSL does seem to have a separate globalState than using it under the host windows, so that *shouldnt* be the cause, but you never know. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5998 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBACRG6ACBIMWQ6QAYF2NDSGFGJXANCNFSM4RLRFMRA> .

[owen-hope]

The issue seemed to be resolved when I quit vscode and had a new update for the rust-analyze to v0.2.313

[kjeremy]

@shenshouer @fuyumatsuri @guzongmin

Do you still see this?

[guzongmin]

@shenshouer @fuyumatsuri @guzongmin

Do you still see this?
Thanks. It works now.

[shenshouer]

It worked after I reinstall rust-analyzer

[Joneyao]

It also worked just restart rust-analyzer.

[briankung]

I've been getting this error for the past few weeks. I've tried restarting and reinstalling rust analyzer as well as updating VS Code. I'm on a Mac.

[towry]

Keep getting this error.