Repository navigation
fix(recovery): match write-set locks to repository plans - #226
Merged
Merged
Conversation
Normalize repository write-set lock scopes during interrupted-operation recovery and refresh the generated projection digests.
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.
Summary
Recovery compared an operation lock's exact write-set scope (
repository-id:target) with the plan's bare repository id. Every interrupted write-set operation was therefore classified as foreign and could not release an expired dead-owner lock. This signed GitHub-generated commit normalizes both representations while preserving strict repository scope checks, refreshes the generated projection digests, and includes a regression test.Validation
go test ./core/app ./core/statego test ./core/assurance ./core/context ./core/cli