Review fixes for incremental indexing PR #592#1144
Closed
azeemshaik025 wants to merge 3 commits into
Closed
Conversation
Computes per-file SHA-256 hashes during indexing and stores them in meta.json. On subsequent runs with --incremental, only files with changed hashes are re-parsed. Structure scanning and graph phases still run fully to ensure correct community/process detection. For large repos (60K+ symbols), this reduces re-index time from ~30s to ~2-5s when only a few files changed between sessions. New files: - src/storage/file-hasher.ts: computeFileHashes() and diffFileHashes() Modified: - src/cli/index.ts: Register -i/--incremental CLI flag - src/cli/analyze.ts: Forward incremental option to runFullAnalysis - src/core/run-analyze.ts: Load previous hashes, pass to pipeline, save new hashes, incremental LadybugDB merge (delete stale nodes instead of wipe-and-recreate) - src/core/ingestion/pipeline.ts: Accept previousFileHashes, filter parse phase to changed files only, return fileHashes in result - src/types/pipeline.ts: Add fileHashes to PipelineResult - src/storage/repo-manager.ts: Add fileHashes to RepoMeta
Two-stage build: builder installs deps + compiles, slim image has only git + gitnexus CLI. Entrypoint indexes all repos in /data/repos/ and starts the eval-server on port 3456. Supports GITNEXUS_INCREMENTAL=1 env var to enable --incremental on container restart (skips unchanged files).
|
@azeemshaik025 is attempting to deploy a commit to the NexusCore Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
Closing this PR so I can recreate it from the same fix commit with a non-codex branch name. |
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.
Companion PR for #592.
I could not push the fix directly to the contributor fork branch even though the PR metadata allows maintainer edits: GitHub denied write access to zenprocess/GitNexus for azeemshaik025. This branch is based on the PR #592 head and adds the review-fix commit on top.
Changes in the added fix commit:
Reviewer item note:
Validation:
Guardrail note: