Cairn

Fix artifact timestamp unit conversion seconds to ms

NousResearch/hermes-agent · cluster 73454 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #86749. Check it covers your case.

The short answer

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

These issues and PRs address a bug where Unix epoch timestamps in seconds were being passed directly to JavaScript's Date(), which expects milliseconds, causing incorrect artifact timestamp rendering in the desktop artifacts panel.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

  • #86749 fix(desktop): artifacts panel 1970 timestamps, over-indexing, and local image display

    merged to main

    files: apps/desktop/src/app/artifacts/artifact-utils.ts, apps/desktop/src/app/artifacts/index.test.ts, apps/desktop/src/app/artifacts/index.tsx, contributors/emails/[redacted:email]

4 PRs closed without merging

From the close comments: done elsewhere 3 · merged via another change 1

  • #42221 fix(artifacts): convert DB timestamps from seconds to ms for Date() · merged via another change → #86749
  • #42415 fix(desktop): convert epoch seconds to ms in artifact timestamp rendering · done elsewhere → #86749, #42221
  • #48577 fix(desktop): clean artifacts timestamps and browser assets · done elsewhere → #86749, #42221
  • #73457 fix(desktop): normalize artifact timestamps · done elsewhere → #86749, #42221
Closed issues · 1
  • Closed#73454Desktop Artifacts panel treats Unix-second timestamps as milliseconds
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
apps/desktop
Merged PRs
#86749
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
15 Aug 2026

For your agent

The same facts, typed.

cluster/73454.json
cluster/73454.md