Repository navigation
A burst of graph events refetches the graph once, not once per event - #263
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Merged
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.
Symptom
While documents are being extracted, the graph page refetches
graph/overviewover and over. Right after uploading three short documents to a fresh base, the network panel showed 16 identical overview requests within a couple of seconds. Each extracted fact emits agraphevent, anduseKbEventsinvalidated the query on every one of them.Change
useKbEventsno longer invalidates on each event. It records the affected query keys and flushes them once the stream has been quiet for 300 ms, so a burst of events costs one refetch, and that refetch necessarily includes every change in the burst. Idempotence is unchanged; only the cadence is. On unmount the pending keys are flushed rather than dropped, so coming back to a page still shows fresh data.Verification
A/B on the same backend with both frontends open on the graph page of the same base, then one document uploaded:
A cold load of the graph page still issues exactly one request.
pnpm buildpasses.No issue was filed for this; it was noticed while testing #259.
🤖 Generated with Claude Code