Repository navigation
Keep conversation import recovery within its original source folders - #725
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.
When processes sharing the import database use different configured source folders, a recovery worker can plan another process's batch using its own files. This added four DGX conversations to an authorised Mac snapshot and published misleading source totals.
Bind each new batch to a digest of its server-configured provider roots. Recovery workers with a different discovery scope leave planning to a matching worker; processing already-planned paths remains unchanged. The digest stays in private controller state.
Validation: 10 targeted bulk-import tests pass, including foreign-root exclusion and recovery when the original roots are restored. This repairs the observed import path; it does not add a new importer or schedule.
The live reconciliation also found one unchanged transcript with a missing raw-file pointer. Compare that pointer before treating a re-import as unchanged, so a valid ingestion receipt repairs it without replacing transcript content. The combined targeted suite passes 42 tests.