fix(episodic): catch LanceError in router search, degrade gracefully (#160)#163
Open
relunctance wants to merge 1 commit intoFlowElement-ai:mainfrom
Open
fix(episodic): catch LanceError in router search, degrade gracefully (#160)#163relunctance wants to merge 1 commit intoFlowElement-ai:mainfrom
relunctance wants to merge 1 commit intoFlowElement-ai:mainfrom
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.
Fix: LanceDB search fails with Invalid range error (#160)
Problem: Episodic router crashes with
LanceError(IO): Generic memory error: Invalid range 0..0 for object of size 0 byteswhen searching Episode_summary/Facet_search_text/Facet_anchor_text tables that are empty or corrupted.Root cause: LanceDB raises this error when searching an empty table or a table with corrupted data (0-byte objects). This is not caught by the existing
_search_collectionexception handler.Solution: Add
lancedb.LanceErrorto the exception handling in_search_collection:When this error occurs, episodic routing degrades to creating a new Episode instead of crashing. This is safe since the ingested data is still in LanceDB — only the routing decision is affected.
Closes #160