feat: add context_chat:reindex to re-seed the crawl on demand#246
Conversation
The SchedulerJob -> StorageCrawlJob -> IndexerJob chain is seeded only by the <install> repair step and self-removes after the initial crawl, so there is no way to re-enumerate mounts without reinstalling the app (e.g. after installing on an instance whose files predate the app, or to recover an incomplete crawl). Add an occ command that re-adds SchedulerJob (no-op if already scheduled); already-indexed files are skipped by the queue de-duplication. Refs nextcloud#244 Signed-off-by: Yoan Bozhilov <bygadd@gmail.com> Assisted-by: Claude Code:claude-opus-4-8
Reword the class docstring and the command description per review feedback. Signed-off-by: Yoan Bozhilov <bygadd@gmail.com> Assisted-by: Claude Code:claude-opus-4-8
|
applied the three suggestions, thanks for the review! |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
|
the NC master branch integration test failures are expected, will be fixed in a different PR. |
|
Thanks for confirming the master integration failures are unrelated — good to know. |
|
updating the PR with a merge commit so the latest context_chat changes are in for the integration test to pass for non-master branches |
|
well, CI to be looked at later. |
2 participants
Follow-up to #244. The
SchedulerJob → StorageCrawlJob → IndexerJobchain is seeded only by the<install>repair step and removes itself after the initial crawl, so there's no way to re-enumerate mounts without reinstalling the app — e.g. when the app is installed on an instance whose files predate it, or to recover a crawl that didn't finish.This adds an
occ context_chat:reindexcommand that re-addsSchedulerJob, guarded so it's a no-op when one is already scheduled. Already-indexed files are skipped (the queue de-duplicates), so it's safe to run repeatedly.(Disclosure: AI-assisted; verified on a live deployment.)