paritytech/soketto

ReservedOpCode error

Closed this issue · 3 comments

While using jsonrpsee we see the Ws(Codec(ReservedOpCode)) error occurring. Currently we use a modified version of jsonrpsees master branch, which exits the application on inner errors, which includes the aforementioned error. Unfortunately it's not easy in jsonrpsee to match only the disconnects, due to the code being generic over errors. Would it make sense at all for us to continue communication when we get a ReservedOpCode? I think we will have missed a message for sure, but other than that, would the library recover if we ignore the error?

I think this is related to that the jsonrpsee ws client is incorrectly designed w.r.t soketto Receiver is not cancel-safe, thus if you could check to logs if something else weird happens before the ReserverdOpCode that would be good and seems likely IMHO.

@sander2 is this still relevant with the latest version of jsonrpsee?

Closing as stale.