Repository navigation
test(sync): two idle replicas exchange no segments after the first round (T13256) - #1968
Merged
Merged
Conversation
…und (T13256) Spec §3.5 R7-7: after one real write each and a first sync round, four more idle rounds of cloud sync on both devices send nothing and the stream's segment count holds; both stores converge. Mutation-checked: disabling the sealer's apply-echo subtraction makes A send a segment in round 0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nit) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pong Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Task: T13256
Stacked on #1967 (feat/T13312-journal-join), which provides the two-device join.
What
This adds the spec §3.5 R7-7 acceptance test, "two idle replicas pulling in a loop exchange no segments after the first round", on the fake server:
cloudSyncround carries both writes.sent === 0on both devices, and the stream's segment count holds.There is no production change. Today no watermark control transaction exists, and the apply's echo is subtracted (§3.3), so idle replicas are already quiet. This test pins that, so the receive-watermark work (T12815/T12810) must piggyback rather than ping-pong.
Verification
sealer.ts, theg.kind === 'apply'branch) fails it with "round 0: A sent: expected 1 to be 0".lint-changesets: passes.🤖 Generated with Claude Code