fix(cli): tolerate fts errors in search#438
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
5572fb7 to
d583b14
Compare
|
Retargeted this PR to |
What changed
Makes
vouch searchtolerate FTS5/index failures the same way the context, MCP, and JSONL retrieval surfaces already do:autobackend falls through to substring search whenindex_db.search()raisessqlite3.Errorhybridbackend degrades to semantic-only fusion when FTS5 raisesWhy
The CLI search path had a resilience gap: server/JSONL/context callers already guard FTS5 failures, but the CLI could still surface a raw search failure instead of returning the best available fallback results.
Tests
PYTHONPATH=src python3 -m pytest tests/test_cli.py -quv run --with ruff python -m ruff check src testsuv run --with mypy --with types-PyYAML --with jinja2 python -m mypy src