Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Responding to Serialization Errors #257

Open
mitsuhiko opened this issue Feb 11, 2020 · 0 comments
Open

Responding to Serialization Errors #257

mitsuhiko opened this issue Feb 11, 2020 · 0 comments

Comments

@mitsuhiko
Copy link

mitsuhiko commented 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." })

@mitsuhiko mitsuhiko changed the title Responding to Serilization Errors Responding to Serialization Errors Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant