feat(review): raise the RAG per-repo chunk cap from 1500 to 4000 - #4398
Merged
Conversation
All 3 currently-gated repos were sitting at the old cap, and gittensory's own indexable tree is within range of it before accounting for large files splitting into multiple chunks -- real code was silently never indexed. Storage/search cost at this scale is trivial for Qdrant regardless of cap size; the higher embedding-compute cost is now one-time per file instead of recurring every cron cycle (#4365's blob-SHA skip-cache).
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4398 +/- ##
=======================================
Coverage 93.96% 93.96%
=======================================
Files 401 401
Lines 36869 36869
Branches 13480 13480
=======================================
Hits 34644 34644
Misses 1569 1569
Partials 656 656
🚀 New features to boost your workflow:
|
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.
Summary
MAX_CHUNKS_PER_REPO(the hard per-repo bound on stored RAG vectors) raised from 1500 to 4000.Scope
wantedPaths(src/)site/,CNAME,**/lovable/**, orCHANGELOG.mdValidation
npm run typechecknpx vitest run test/unit/rag.test.ts test/unit/rag-index.test.ts— 127/127 passing (every cap-related test references the exported constant, none hardcode the old value)npm run db:schema-drift:check/npm run selfhost:env-reference:check— clean (no schema/env surface touched)npm audit --audit-level=moderate— 0 vulnerabilitiesSafety