NousResearch/hermes-agent

Analytics daily chart timezone offset bug fixes

Cluster 23982 · dashboard. Data as of 2026-10-26 12:29 UTC

1 open item. Fix merged in #126249 on 28 Sep 2026. Check it covers your case.

open issue

open PRs

items grouped

Known?: Yes. 6 related items grouped here, 0 issues already closed.
Fix event: A fix was merged to main in PR #126249. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 1 issue and 0 PRs.

Next step: read #126249, then check whether your report is the one still open.

Read #126249 Pick up a Lab task

A bug where dashboard analytics grouped data by UTC instead of the user-configured timezone, plus related fixes for a zoneinfo utcoffset() call requiring a datetime argument rather than None.

Open issues1

Issue#23982Dashboard analytics daily chart uses UTC instead of configured timezone

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#126249 fix(analytics): daily usage buckets use local days, matching /insights

merged to main

files: hermes_cli/web_routers/analytics.py, tests/hermes_cli/test_web_server.py

4 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · duplicate 1 · superseded by another PR 1

#24030 fix(analytics): pass datetime to utcoffset() — zoneinfo returns None with bare None arg · closed without comment
#24031 fix(analytics): pass datetime to utcoffset() — zoneinfo returns None with bare None arg · duplicate → #24030, #23981
#62317 fix(dashboard): group analytics by configured timezone · superseded by another PR → 8790d03, #23982, #126249
#76764 fix: use user-configured timezone for dashboard analytics daily grouping · done elsewhere

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: dashboard
Merged PRs: #126249
Closed issues: 0
Attempts: 4 PRs closed without merging
Fix link checked: 28 Sep 2026

For your agent

The same facts, typed.

cluster/23982.json
cluster/23982.md