Serialize duplicate publication items within batches#772
Merged
Conversation
hxy91819
marked this pull request as ready for review
July 22, 2026 04:41
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: Serialize duplicate publication items within batches This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
This was referenced Jul 23, 2026
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
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.
Summary
targetRepo#itemNumberacross batch commitsRoot cause
The first size-8 production claim contained two distinct queue events for
openclaw/openclaw#108676. Their queue identities and revisions were independent, but both prepared mutations for the same durable record path. Combining those plans in one state commit raisedStateMutationConflictErrorbefore state was written.Batch claim admission now selects at most one event for each logical durable item. A later event remains pending and can be selected by the next batch.
The separate failure in run 29890705127 (
commit_refsrejection followed by an innerinvalid_batch_state_writer_identity) is documented as an independent re-advance gate rather than attributed to this root cause.Validation
pnpm run checkpassedAfter deployment, the rollout remains at size 4 until a safe live recovery sample proves duplicate-target serialization and deferred consumption. Size 8 will return in a separate reviewed PR only after that gate passes.