fix: atomic watcher updates and removals (1.17.2) - #43
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.
Individual watched updates/removals could still mutate the active vector table before committing metadata. Stage these mutations, validate the complete staged count, and atomically activate the new metadata pointer. This also covers files becoming ignored, generated or empty. On failure, preserve the previous generation and discard unactivated staging.
Validation: typecheck; 243 passing tests including persistence, metadata-commit and count-mismatch failures; real Windows/Ollama subprocesses terminated immediately before metadata activation for both updateFile and removeFile preserved the previous snapshot, then recovered successfully. Release core/CLI/MCP 1.17.2. No search/ranking changes.