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
As a developer, I would like to receive a usable error when I send something that does not fit with the current protocol specification so that I can have an easier time debugging clients and taking into account protocol changes.
Currently when sent something that cannot be decoded into the protocol (type:boolean,len:int,msg) then I do not receive anything back as a response, with the following error on the server:
As a developer, I would like to receive a usable error when I send something that does not fit with the current protocol specification so that I can have an easier time debugging clients and taking into account protocol changes.
Currently when sent something that cannot be decoded into the protocol (type:boolean,len:int,msg) then I do not receive anything back as a response, with the following error on the server:
When the protocol object cannot be fully decoded, I would like to receive an exception telling me that.
The text was updated successfully, but these errors were encountered: