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
It would be nice to be able to be able to respond to these errors in a way that lets you still send something into the channel so that the receiver can deal with the errors.
I tried using the channel a second time after send() which seems to work because the bincode serialization fails internally when filling the buffer, before actually sending but I believe something corrupts internally which seem to cause errors like this: Io(Custom { kind: NotFound, error: "Bogus destination port." })
The text was updated successfully, but these errors were encountered:
mitsuhiko
changed the title
Responding to Serilization Errors
Responding to Serialization Errors
Feb 11, 2020
Due to bincode-org/bincode#245, bincode-org/bincode#167 and a few others it's not uncommon that one can end up in a situation where objects fail to serialize.
It would be nice to be able to be able to respond to these errors in a way that lets you still send something into the channel so that the receiver can deal with the errors.
I tried using the channel a second time after
send()
which seems to work because the bincode serialization fails internally when filling the buffer, before actually sending but I believe something corrupts internally which seem to cause errors like this:Io(Custom { kind: NotFound, error: "Bogus destination port." })
The text was updated successfully, but these errors were encountered: