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

[RFC-001] Define semantics of unexpected body #10

Closed
thomaseizinger opened this Issue Aug 31, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@thomaseizinger
Copy link
Member

thomaseizinger commented Aug 31, 2018

Note: Implementation defined behaviour.

@bonomat

This comment has been minimized.

Copy link
Member

bonomat commented Dec 18, 2018

@thomaseizinger : is this related to RFC003 or BAM! ?

@thomaseizinger

This comment has been minimized.

Copy link
Member Author

thomaseizinger commented Dec 18, 2018

@thomaseizinger

This comment has been minimized.

Copy link
Member Author

thomaseizinger commented Dec 18, 2018

As the title says, probably rfc003 :)

@bonomat bonomat transferred this issue from another repository Dec 18, 2018

@D4nte

This comment has been minimized.

Copy link
Member

D4nte commented Dec 26, 2018

I guess if it's unexpected body it means BAM was able to deserialize the message.

comit-network/comit-rs#603 tracks implementation of deserialization error at BAM level. I'd expect an update of BAM RFC as part of it.

@D4nte D4nte changed the title [RFC-003] Define semantics of unexpected body [RFC-001] Define semantics of unexpected body Jan 30, 2019

@D4nte D4nte added the groomed label Jan 30, 2019

@wafflebot wafflebot bot removed the groomed label Feb 11, 2019

@D4nte D4nte added this to the Sprint 8 👬🥚 milestone Feb 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.