Took a closer look and it seems we also have a different, albeit kind of known bug, where we treat responses to server requests as malformed requests and now we respond with an incorrect "Invalid Request" response.

Here are the messages on init (unstable_features on, omitted "jsonrpc": "2.0" and remaining, long parts with ... for brevity):

Client <--> Server

--> {"id":0,"method":"initialize" ...}
<-- {"id":0,"result":{"capabilities": ...}
<-- {"method":"rustDocument/diagnosticsBegin","params":null}" (build due to init)

--> {"method":"initialized","params":{}} (ignored as invalid: None)
--> {"method":"$/setTraceNotification","params":{"value":"off"}}  (ignored as invalid: None)
--> {"method":"workspace/didChangeConfiguration" ...}
<-- {"method":"rustDocument/diagnosticsBegin","params":null}" (build due to configuration change)
<-- {"id":1,"method":"client/registerCapability" ...} (opt-in to range formatting due to enabled unstable features)

--> {"method":"textDocument/didOpen" ...}

--> {"id":1,"method":"textDocument/codeAction" ...}
<-- {"id":1,"result":[]}
--> {"id":1,"result":null} (response to client/registerCapability, wrongfully treated as invalid request: "Invalid request", id: 1)

...

opt out of build on init #419

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions