fix: close concurrency, recovery, and filesystem gaps in v6.2.10#12
Merged
Conversation
|
Thank you for all the information. |
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.
What changed
Why
The 6.2.9 freshness veto watched only confirmation fields and whole-node writes could still erase concurrent corrections or links. Archive delivery also happened before the graph decision was final. A broader audit found additional stale export, unsafe file-object, resource exhaustion, rendering, crash recovery, cross-platform, and same-process concurrency gaps.
User impact
Normal single-writer use remains compatible. Concurrent writers now preserve semantic operations instead of relying on stale merge heuristics. Unsafe or damaged auxiliary files are skipped or quarantined with explicit warnings. Resource ceilings are documented and enforced.
Verification