fix(search): recover Meilisearch indexes safely - #21
Conversation
Co-authored-by: multica-agent <github@multica.ai>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 20f12cc83a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Co-authored-by: multica-agent <github@multica.ai>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f7317c8cac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Co-authored-by: multica-agent <github@multica.ai>
Summary
series.numuniqueness assumption that broke provider refreshes.Root Cause
Provider series ordering changed, causing existing records to temporarily share
numvalues during upsert. SQLite rejected refresh withUNIQUE constraint failed: series.num. Search indexes had already been flushed, leaving both indexes empty after database sync aborted.Recovery
php artisan lionz:reconcile-search --forcefor manual recovery.Verification
337 passedUnit/Feature tests,2,866 assertions.2 passed,8 assertions.SyncCategories,MediaCategoryAssignment, andUserCategoryPreference.Related: ZRO-1