Skip to content

Ensure we call operation on the most recent view#444

Draft
Ph4ntomas wants to merge 1 commit intopinnacle-comp:mainfrom
Ph4ntomas:443-operate-msg-ordering
Draft

Ensure we call operation on the most recent view#444
Ph4ntomas wants to merge 1 commit intopinnacle-comp:mainfrom
Ph4ntomas:443-operate-msg-ordering

Conversation

@Ph4ntomas
Copy link
Copy Markdown
Contributor

problem: it's possible for operate() call to apply on a stale view if a view is pending, leading to some operation failing.

solution: There are two part of this fix:

  1. Enforce ordering of update and operate message by using the message queue used by message
  2. Delay sending operate calls to the server until after the view was sent.

Fixes: #443

problem: it's possible for operate() call to apply on a stale view if a
view is pending, leading to some operation failing.

solution: There are two part of this fix:
1. Enforce ordering of update and operate message by using the message
   queue used by message
2. Delay sending operate calls to the server until after the view was
   sent.
@Ph4ntomas Ph4ntomas changed the title snowcap/rust: Ensure we call operation on the most recent view Ensure we call operation on the most recent view Mar 15, 2026
@Ph4ntomas Ph4ntomas force-pushed the 443-operate-msg-ordering branch from 1cb61bd to 10e063d Compare March 15, 2026 20:14
@Ph4ntomas
Copy link
Copy Markdown
Contributor Author

Okay this works as far as I can tell, but I need to check/implement the lua side

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

Successfully merging this pull request may close these issues.

[Snowcap] Wrong ordering of events when sending messages and operation.

1 participant