Skip to content

fix(recovery): match write-set locks to repository plans - #223

Closed
rldyourmnd wants to merge 2 commits into
mainfrom
fix/recovery-lock-scope-20261009
Closed

rldyourmnd wants to merge 2 commits into
mainfrom
fix/recovery-lock-scope-20261009

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

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. Normalize both representations while preserving strict repository scope checks, and add a regression test.

Validation

  • go test ./core/app ./core/state
  • built temporary patched GDS and successfully planned/applied/verified recovery of the interrupted RDS pin journal

The local signing key was unavailable on this workstation; the change is otherwise an atomic Conventional Commit and must pass the repository's required review/checks before merge.

@rldyourmnd
rldyourmnd enabled auto-merge October 9, 2026 00:56
@rldyourmnd rldyourmnd closed this Oct 9, 2026
auto-merge was automatically disabled October 9, 2026 00:59

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant