fix(tui): update graph metrics every turn, not only on extraction#1934
Merged
fix(tui): update graph metrics every turn, not only on extraction#1934
Conversation
sync_graph_counts() was only called from persistence.rs after a graph extraction event fired, leaving entity/edge/community counts at zero on startup and during turns that do not trigger extraction. Add a per-turn call to sync_graph_counts() in process_user_message_inner, after analyze_and_learn(). Startup calls (check_vector_store_health and sync_graph_counts in runner.rs) were already present. Closes #1932
github-actions
bot
added
documentation
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.
Summary
sync_graph_counts()was called only frompersistence.rsafter a graph extraction event, leaving entity/edge/community counts at zero on startup and during turns that do not trigger extractionsync_graph_counts()inprocess_user_message_innerafteranalyze_and_learn()— startup calls (check_vector_store_health+sync_graph_countsinrunner.rs) were already in placeTest plan
cargo build --features fullcargo clippy --workspace --features full -- -D warningscargo nextest run --config-file .github/nextest.toml --workspace --features full --lib --bins(6098 passed)[memory.graph] enabled = true, have a conversation to populate graph data, restart agent, open TUI — entity/edge/community counts should reflect actual DB values immediatelyCloses #1932