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
Currently State::add_message_in() has no return value and panics on any error. We need to properly handle errors. Errors can be one of two types:
Party error. (eg. failure to deserialize.) A party has done something bad. This kicks the protocol into fault attribution mode. No error should be returned in this case.
Caller error. (eg. repeated message.) No party has done something bad, so don't kick the protocol into fault attribution mode. The caller must have screwed something up. In this case, either return an error or panic.
Currently
State::add_message_in()
has no return value and panics on any error. We need to properly handle errors. Errors can be one of two types:Originally posted by @sergeynog in #1 (comment)
The text was updated successfully, but these errors were encountered: