Repository navigation
fix: count each session once and apply a new rescan interval straight away - #32
Merged
Merged
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.
Category
Bugfix
Overview
The session counts on the Tools and Projects panels counted a session once for every model it used. A Claude Code session running Opus with Haiku subagents turned up twice, so on my data Claude Code read 4,144 sessions all time when there are 3,974, and Projects ranked by sessions was off too (brain 3,389 vs 3,265). The headline figure already got it right.
Changing "Rescan every" in settings also did nothing until a restart, because the timer only read the setting once at start-up. It's restarted on save now.
Two small ones while I was in there: "The scan stopped early" never cleared once a later scan went fine, and
PORT=abc aiusagesaid "null is not a port".Issue Number
n/a
Additional Info
On a copy of my live database every other number on the page matches main, and a full rollup takes the same time. The new test fails on main. Run side by side with main's build and switched to 30 seconds, this branch rescanned at +30s and +61s while main kept waiting on its two minute timer.