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
{{ message }}
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
To better handle error conditions and unexpected behaviour, we should implement common exception types, and some handlers for cases where a usual course of action needs to be taken.
The RPC method should always be handling the received exceptions and setting the error key in the response message (or handling, if it is appropriate for the method)
Types of issue
Feature request (request for change which adds functionality)
Expected Behavior
Local methods should not set an error key in the RPCMessage response
RPC callbacks should set the error key in the RPCMessage response in the event of an exception or error in the local method
Current Behavior
Some local methods return error codes, some set the error key, and some throw an exception.
The text was updated successfully, but these errors were encountered:
Brief summary of issue
To better handle error conditions and unexpected behaviour, we should implement common exception types, and some handlers for cases where a usual course of action needs to be taken.
The RPC method should always be handling the received exceptions and setting the
error
key in the response message (or handling, if it is appropriate for the method)Types of issue
Expected Behavior
error
key in theRPCMessage
responseerror
key in theRPCMessage
response in the event of an exception or error in the local methodCurrent Behavior
Some local methods return error codes, some set the
error
key, and somethrow
an exception.The text was updated successfully, but these errors were encountered: