You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging VS I was innoudated with JsonRpc warnings that No target methods are registered that match "NotificationRequested" (see azdo 2341995)
When monitoring traffic between the LSP Client and Server I noticed that the response to workspace/SemanticTokens/refresh notification has invalid json; I think for this to work correctly (and not produce warnings), the response should be "method": "workspace/SemanticTokens/refresh". Currently, it is "method": "NotificationReceived" with "params.MethodName": "workspace/SemanticTokens/refresh"
The text was updated successfully, but these errors were encountered:
Indeed the string "NotificationReceived" doesn't appear in our repo anywhere. I'm also seeing these same messages logged for the Roslyn server too:
Are you sure this is coming from us? I could see this happening if something is sending this message to us, as we don't support that method, so the log message makes sense. We send it to the client, but perhaps there is something out there that is blasting that message to all clients? The method that I'm debugging in that screenshot is "DispatchIncomingRequest"
I couldn't see a way to identify any of that in the debugger though.
When debugging VS I was innoudated with JsonRpc warnings that
No target methods are registered that match "NotificationRequested"
(see azdo 2341995)When monitoring traffic between the LSP Client and Server I noticed that the response to
workspace/SemanticTokens/refresh
notification has invalid json; I think for this to work correctly (and not produce warnings), the response should be"method": "workspace/SemanticTokens/refresh"
. Currently, it is"method": "NotificationReceived"
with"params.MethodName": "workspace/SemanticTokens/refresh"
The text was updated successfully, but these errors were encountered: