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

#252: Discuss Welcome/Commit coupling #255

Merged
merged 2 commits into from
Jun 13, 2024
Merged

#252: Discuss Welcome/Commit coupling #255

merged 2 commits into from
Jun 13, 2024

Conversation

Bren2010
Copy link
Contributor

@Bren2010 Bren2010 commented Jun 5, 2024

No description provided.

Comment on lines 816 to 820
of the previous group's members). However this operation is not always atomic,
so it's possible for a member to go offline after committing a ReInit proposal
but before creating the new group. When this happens, it's necessary for another
member to continue the reinitialization by creating the new group and sending
out Welcome messages.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it is possible to design a client that does that, but it is also possible to design ones that always do generate the new group atomically. Is there a technical reason to NOT generate the ReInit Commit and create the new group as a single step?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's not a technical reason to make it not atomic. Like you say, it's possible, and doing so would avoid this issue. But I don't think it's something worth requiring

@ekr ekr merged commit 3a09ca7 into mlswg:main Jun 13, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants