fix: recover stale docker sync owners#72
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
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
MetadataStoreReview notes
contextwiki_datavolumerunningsync rows without touching document/chunk content or Chroma dataVerification
uv run --locked pytest -q tests/storage/test_metadata_store.py -k "same_pid_previous_owner or stale_previous_owner_even_if_pid_looks_alive or live_previous_owner or previous_owner or begin_sync_job_preserves_same_pid_previous_owner or begin_sync_job_recovers_stale_same_pid_previous_owner"uv run --locked pytest -q tests/storage/test_metadata_store.pypython -m compileall api core environments fetching indexing search storage main.py./scripts/verify_functional_e2e.sh관련 이슈 없음