Repository navigation
fix: fail loudly on non-1536-dim local embeddings (#84) #95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MAJOR — declared behavior vs actual: API startup does not fail here, it logs and continues.
The README (
Vectors are stored…API startup fail with an actionable message),.env.example(startup and \ingest --with-embeddings` fail with an actionable message), and this PR's own acceptance criterion (fails loudly at startup/ingest) all state that a non-persistable embeddings config makes **API startup fail**. But this handler catchesEmbeddingsConfigErrorand only emits oneerrorlog, thenyield`s — the app boots and serves normally.CONFIRMED asymmetry with the ingest path, which genuinely fails:
src/cli/commands/ingest.py:74doesraise typer.Exit(1)on the same error. So "fails loudly at startup/ingest" is true for ingest, false for the API.Operational consequence: an operator who deploys the API with
EMBEDDINGS_PROVIDER=local+ a 384/768-dim model (the exact case #84 is about) gets a green, healthy-looking server that will never persist a vector and silently keyword-falls-back on/v1/query/similarand semanticask— with only a single startup log line, which is easy to miss. That's close to the silent no-op the issue set out to eliminate.Two clean resolutions — pick one:
raise/raise RuntimeError(...)) so the process refuses to boot on a broken config. Note this couples the whole API's availability to an optional feature, which may be too aggressive during an incident..env.exampleto say the API logs the misconfig aterroron startup and continues serving non-embedding features, and onlyingest --with-embeddingshard-exits. That keeps explain/timeline/compare available while still being non-silent.Either way, docs and code should agree. Right now they don't.