Repository navigation
Prevent functional battery from overwriting staged user exports - #60
Merged
Merged
Conversation
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.
The first rc-26 extraction unexpectedly contained only
exchange/.exp-probebecause the functional battery runs a regular path-modelabloop-exportand replaces the user's staged manifest/tarball. Addlabloop-export --self-test <exchange-file>with a private mktemp staging area under the already owner-restricted export directory, shared serialization lock, archive/hash/manifest verification, and cleanup on exit. Switch battery to self-test; document why default extraction prefers a staged user path-mode snapshot and how to explicitly request--all. Tests ensure battery cannot overwrite normal staging. This addresses the confirmed data-lifecycle defect, not historical LightDM/OpenCode warnings.