Skip to content

fix(reports): reissue a cached report when more of its calls are analysed - #9

Merged
Frekion2002 merged 1 commit into
mainfrom
fix/report-snapshot-late-analysis
Nov 5, 2026
Merged

Frekion2002 merged 1 commit into
mainfrom
fix/report-snapshot-late-analysis

Conversation

@Frekion2002

Copy link
Copy Markdown
Collaborator

A report opened while a call was still being analysed was cached without that call, and the cache kept serving it after the analysis finished because the call's end time was earlier than the snapshot. Past periods were never reissued, so a Sunday-night call analysed on Monday stayed out of last week's report.

The snapshot is now reused only while its analyzedCallCount matches the analysed calls in the period. No migration; snapshots without the field are rebuilt once.

Tests: two regression tests (fail before the fix), full suite 341 passed, ruff clean.

…ysed

Analysis finishes a few minutes after a call ends. A report opened in that
window was cached, and because the call's end time was earlier than the
snapshot the cache kept serving it without the new analysis. Past periods
were never reissued at all, so a Sunday-night call analysed on Monday stayed
out of last week's report.

Reuse the snapshot only when its analyzedCallCount still matches the
analysed calls in the period. No migration; snapshots without the field are
rebuilt once.
@Frekion2002
Frekion2002 merged commit 93074d1 into main Nov 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant