-
Notifications
You must be signed in to change notification settings - Fork 0
fix(state): review follow-ups from #142/#149 — idempotency ordering, head verification, replay across migrations #171
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
Merged
Merged
Changes from all commits
Commits
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| --- | ||
| "@agent-bundle/runtime": patch | ||
| --- | ||
|
|
||
| State kernel review follow-ups from #142/#149. Both drivers now consult the | ||
| idempotency key before running the reducer, so a committed key replays its | ||
| stored result even when the reducer would fail against the current head; the | ||
| committed result is stored per key (event journal rows now persist their | ||
| post-commit state) and rides the migration chain, so replay survives schema | ||
| migrations instead of failing `revision-unavailable`. The sqlite driver | ||
| verifies storage on open — journal continuity (a hand-deleted intermediate | ||
| row fails closed) and the materialized head against journal replay (a | ||
| schema-valid but hand-edited head fails closed) — and derives database file | ||
| names from a sha-256 hash of the complete definition id, so ids that share a | ||
| sanitized prefix no longer collide onto one file. Sparse arrays are rejected | ||
| at the JSON boundary instead of silently canonicalizing like dense ones. The | ||
| shared conformance suite pins the corrected semantics for every driver. |
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
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
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.
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.
If migration succeeds for the head but throws for a later historical committed result, this loop has already replaced earlier map entries in place, and the migration record was already appended. The rejected
open()consequently leaves the process store partially migrated; retrying with a corrected migration appends another record at the same revision and migrates some entries twice. Build the migrated key map and record without mutatinginternals, then swap all fields only after every migration succeeds.Useful? React with 👍 / 👎.
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.
Fixed in #201 (merged as ae7722c).
migrateOpenStorenow builds the migrated keys map fully before swapping it in; the journal/head/definition updates also happen only after every per-key migration succeeded, so a throwing migration leaves the store exactly as it was. Regression test: a migration that throws on one historical result leaves reads, change feeds, and idempotent replay intact, and a later successful migration still works.