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 we stash errors like payload checks, protocol errors, block size checks, etc in io::Error. However, tokio_io::codec::Decode and tokio_io::codec::Encode would allow us to specify some wrapper error.
Currently we store informative strings in the custom error type, so its not too difficult to track down why we severed a peer connection, but if we want client to be able to easily check why we severed the connection, and ban peers based on this, we need to export some enum of all possible error types they may want to ban on (as well as a catch all io::Error variant).
The text was updated successfully, but these errors were encountered:
Currently we stash errors like payload checks, protocol errors, block size checks, etc in
io::Error
. However,tokio_io::codec::Decode
andtokio_io::codec::Encode
would allow us to specify some wrapper error.Currently we store informative strings in the custom error type, so its not too difficult to track down why we severed a peer connection, but if we want client to be able to easily check why we severed the connection, and ban peers based on this, we need to export some enum of all possible error types they may want to ban on (as well as a catch all
io::Error
variant).The text was updated successfully, but these errors were encountered: