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

Clarify how to handle redundant messages in ABA #10

Open
sbellem opened this issue Jul 3, 2018 · 1 comment
Open

Clarify how to handle redundant messages in ABA #10

sbellem opened this issue Jul 3, 2018 · 1 comment
Assignees
Milestone

Comments

@sbellem
Copy link
Collaborator

sbellem commented Jul 3, 2018

Currently, upon reception of an EST or AUX message a node will raise an error if the message (of the form (tag, round, value), e.g.: ('EST', 0, 0)) has already been received by the sender.

This issue is meant to clarify whether this is what the protocol implementation should really do, or whether it should simply silently discard the message and continue looping to receive messages.

@sbellem
Copy link
Collaborator Author

sbellem commented Jul 5, 2018

From a discussion with @amiller, for now we'll simply log the information regarding the redundant message and continue looping.

Will leave this issue open until the required changes are merged.

@sbellem sbellem added this to the 1.0 milestone Aug 24, 2018
@sbellem sbellem changed the title clarify how to handle redundant messages in BA clarify how to handle redundant messages in ABA Aug 29, 2018
@sbellem sbellem changed the title clarify how to handle redundant messages in ABA Clarify how to handle redundant messages in ABA Aug 29, 2018
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

2 participants