[codex] Bound graph API construction by limit#499
Draft
hnabyz-bot wants to merge 1 commit into
Draft
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
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.
What changed
limitbefore edge expansion.qandnodeTypewhile avoiding full-vault link expansion for small graph requests.Why
P1-scale vault smoke testing showed
/api/v1/projects/:id/graph?limit=...timing out because the endpoint scanned and linked the entire vault before truncating the response. This made evenlimit=1unusably slow after a large vault publish.Validation
reports/p1-app-smoke-202606280000in the ops repo.cargo check --lib, the focused graph test, and release build passed.cargo check --libcould not complete because the upstream v0.5.2 build script requires..\mcp-server\node_modules, which is not present on this machine/worktree.