fix(fuse): persist object GC claims in publish journal#404
Closed
wchwawa wants to merge 1 commit into
Closed
Conversation
Signed-off-by: wchwawa <wch19961116@gmail.com>
wchwawa
force-pushed
the
fix/fuse-object-gc-journal
branch
from
July 11, 2026 04:55
61da06a to
6aa2042
Compare
wchwawa
force-pushed
the
feat/workbench-restore-to-fork
branch
from
July 11, 2026 04:55
2ed2106 to
8d0a6ec
Compare
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
Stack and scope
Depends on #403 and is intentionally separate from the Workbench restore delivery.
This is a narrow publish-journal correctness PR. It changes five nokv-fuse files only.
It does not add operator rollback, mutation fencing, SubtreeReplaced invalidation, remote watch support, or a general automatic object-GC refresh and re-upload loop. Broader restage policy remains deferred.
Validation
The added deterministic tests cover zero-token rejection, legacy-record fail-closed behavior, and exact claim reconstruction during recovery.