rust-analyzer: thread '' panicked at 'not implemented', /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9\src\libstd\macros.rs:13:23

Yesterday, using VSCode, I don’t know why, but RA suddenly stopped working at all. No navigation, no semantic highlighting with this error:

thread '<unnamed>' panicked at 'not implemented', /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9\src\libstd\macros.rs:13:23
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: <unknown>
  30: <unknown>
  31: <unknown>
  32: <unknown>
  33: <unknown>
  34: <unknown>
  35: <unknown>
  36: <unknown>
  37: <unknown>
  38: <unknown>
  39: <unknown>
  40: <unknown>
  41: <unknown>
  42: <unknown>
  43: <unknown>
  44: <unknown>
  45: <unknown>
  46: <unknown>
  47: <unknown>
  48: <unknown>
  49: <unknown>
  50: <unknown>
  51: <unknown>
  52: <unknown>
  53: <unknown>
  54: BaseThreadInitThunk
  55: RtlUserThreadStart
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Panic context:
> request: textDocument/definition GotoDefinitionParams {
    text_document_position_params: TextDocumentPositionParams {
        text_document: TextDocumentIdentifier {
            uri: "file:///c%3A/Users/geobe/work/my_project/src/server.rs",
        },
        position: Position {
            line: 44,
            character: 65,
        },
    },
    work_done_progress_params: WorkDoneProgressParams {
        work_done_token: None,
    },
    partial_result_params: PartialResultParams {
        partial_result_token: None,
    },
}

and in extension host logs, this message multiple times:

[2020-10-01 11:20:32.716] [exthost] [error] [matklad.rust-analyzer] provider FAILED
[2020-10-01 11:20:32.717] [exthost] [error] Canceled: Canceled
	at LanguageClient.makeCancelError (c:\Users\geobe\.vscode\extensions\matklad.rust-analyzer-0.3.331-nightly\out\src\main.js:11804:24)
	at LanguageClient.handleFailedRequest (c:\Users\geobe\.vscode\extensions\matklad.rust-analyzer-0.3.331-nightly\out\src\main.js:11794:28)
	at c:\Users\geobe\.vscode\extensions\matklad.rust-analyzer-0.3.331-nightly\out\src\main.js:14748:28

Then I rollback to stable and is was still broken, but after deleting target/rls it started to work again 😕

As it was working again after deleting the target/rls, I switched to nightly again, and it was working… The “provider FAILED” logs in the extension host logs was still present though.

Today, I updated the nightly like everyday, and it was broken again 😕 same errors in boths logs.

Reverted to stable, and it works even if I get the extensions host log:

[2020-10-02 09:30:16.942] [exthost] [error] [matklad.rust-analyzer] provider FAILED
[2020-10-02 09:30:16.943] [exthost] [error] Canceled: Canceled
	at LanguageClient.makeCancelError (c:\Users\geobe\.vscode\extensions\matklad.rust-analyzer-0.2.328\out\src\main.js:11804:24)
	at LanguageClient.handleFailedRequest (c:\Users\geobe\.vscode\extensions\matklad.rust-analyzer-0.2.328\out\src\main.js:11794:28)
	at c:\Users\geobe\.vscode\extensions\matklad.rust-analyzer-0.2.328\out\src\main.js:14742:28

PS: was posted here as well: https://users.rust-lang.org/t/ra-totally-broken-since-1st-oct-version/49529/7

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (15 by maintainers)

Commits related to this issue

Most upvoted comments

It’s fixed in e95e666 🥳

It might be platform-specific. Veetaha is using Linux IIRC, while you’re on Windows. MSVC debug symbols are usually in a different file (.pdb), but I don’t know what we use to build Windows binaries.