SEARCH_INDEX_UNAVAILABLE for locked-index fallback failure#122
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughSearch execution now uses a structured index-search outcome, converts locked-index live-scan failures into ChangesSearch index unavailable handling
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
timon0305
requested changes
Jul 8, 2026
timon0305
approved these changes
Jul 8, 2026
wpak-ai
approved these changes
Jul 8, 2026
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.
Closes #114
Small follow-up after #121.
#121 already falls back to live-scan when the FTS index is locked, and still returns partial hits if it got some before the lock. Here we handle the case it didn't cover: index locked with no hits, and live-scan fails too. That gets 503 SEARCH_INDEX_UNAVAILABLE instead of a generic 500.
We log the real exception in the wrapper before mapping it to the 503. The JSON response keeps a fixed message. Tests also assert that live-scan error text doesn't end up in the body.
Touched error_codes.py, search.py, api-reference, and the search/error tests. pytest and ruff clean on what changed.
Summary by CodeRabbit
/api/searchhandling for temporary search index unavailability, returning HTTP 503 withSEARCH_INDEX_UNAVAILABLE.SEARCH_INDEX_UNAVAILABLEerror code in the API reference.