fix(parser): bound Gemini reconciliation work - #1259
Merged
Conversation
Rehydrate exact Gemini sources from the project hint captured during streamed discovery. This avoids rebuilding root-wide project metadata for every candidate after lost filesystem events.
roborev: Combined Review (
|
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
2 participants
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.
Lost-event recovery rehydrates discovered Gemini sources in bounded pages. Gemini previously routed every candidate back through changed-path classification, rebuilding root-wide project metadata and repeating filesystem and Git resolution once per session. Large recoveries could therefore keep an otherwise idle daemon CPU-bound long after discovery completed.
Teach the Gemini provider to reconstruct the exact discovered source from its spooled path and project hint. This preserves the project selected by authoritative discovery while keeping reconciliation work proportional to the candidate batch. A scaling regression covers both small and larger archives.