-
Notifications
You must be signed in to change notification settings - Fork 18
fix(rust): do not advance session watermark on a replayed commit #162
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
Open
EfeDurmaz16
wants to merge
3
commits into
solana-foundation:main
Choose a base branch
from
EfeDurmaz16:fix/rust-session-replay
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
a9c6a50
fix(rust): reconcile session watermark on a replayed commit; guard fo…
EfeDurmaz16 76fb2c8
fix(rust): advance request nonce when reconciling a replayed settled …
EfeDurmaz16 d19638d
fix(rust): clamp replayed-receipt reconcile to the prepared voucher c…
EfeDurmaz16 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reconcile_settledleaves the nonce counter behindrecord_voucher(the fresh-commit path) advancesself.noncetomax(current, voucher.nonce).reconcile_settledadvances onlyself.cumulative. In the canonical lost-response scenario this creates an immediate nonce collision: the client starts atnonce=0,prepare_increment(X)emits a voucher withnonce=1, the server settles it atnonce=1, the network drops the response, the client retries, getsReplayedat the correct cumulative, callsreconcile_settled— and is now atcumulative=X, nonce=0. The very nextprepare_incrementproduces another voucher withnonce=1, which the server has already accepted. If the channel program or the session server validates nonce monotonicity (which is the whole point of tracking it client-side), that delivery will be rejected.reconcile_settledshould also advance the nonce, either by accepting it as a second parameter or by havingcommit_directivecall a separatereconcile_nonce(payload.voucher.data.nonce.unwrap_or(0))helper on the replay branch. The existing regression tests do not exercise a second delivery after a replay, so the failure mode is invisible today.