Skip to content

fix(ui): ghost sentinel timestamps read as current, not 1970 - #186

Merged
herchu merged 1 commit into
mainfrom
b-herchu/ghost-ts-ui
Oct 15, 2026
Merged

herchu merged 1 commit into
mainfrom
b-herchu/ghost-ts-ui

Conversation

@herchu

@herchu herchu commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

Summary

Ghost robots (updateStamp / ts = HACK_GHOST_UPDATE_STAMP_VALUE, i.e. 12) are already treated as never stale in lib/status.js, but three places still formatted that timestamp with moment and showed "57 years ago":

  • Key Values widget: the sentinel now reads as "recently" and is not marked stale.
  • Robot header: "Last seen just now" instead of "Last seen 57 years ago".
  • Fleet Status chip tooltip: no "(Last reported ...)" suffix for the sentinel.

Independent of #185 (the Robot config kind), which is how ghosts get created; the sentinel itself predates both.

Test plan

🤖 Generated with Claude Code

The Key Values widget, the robot header "Last seen" and the fleet chip
tooltip formatted the ghost sentinel (ts = 12) with moment, so ghost
robots showed "57 years ago". Treat the sentinel as "now" in those three
places, matching the existing handling in lib/status.js.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@netlify

netlify Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for ornate-croquembouche-cc5482 canceled.

Name Link
🔨 Latest commit 923f90f
🔍 Latest deploy log https://app.netlify.com/projects/ornate-croquembouche-cc5482/deploys/6ad11884a6b2bf2faf70f318

@herchu
herchu merged commit a35be8d into main Oct 15, 2026
6 of 7 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