fix: handle JsonRPC error variants as responses #2903
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the message handling block treated only JsonRpcMessage::JsonRpcResponse types with ids as request responses, and all other messages were sent to the notification stream. But, servers may send back a JsonRpcError which is distinct from JsonRpcResponse. This should not be sent to the notification stream.
Also added this to the integration test.
Fixes #2884