Every task's expanded timeline on /tasks reads "No events yet — This task has not recorded any transitions," regardless of status or how far the task progressed. Confirmed live across a Working task and multiple Parked tasks at different stages:
#1000000000000001 — Working, implement/baseline, 20+ minutes in
#1000000000000000 — Parked at implement/baseline (go build/VCS-stamp failure)
#445 — Parked at tdd/commit-push (git push permission error)
All three show the identical empty-timeline message. This isn't isolated to the currently-stuck task — the timeline feature appears non-functional for the whole deployment, which means the dashboard's per-task "what actually happened" view (the thing an operator reaches for first when a task needs attention) carries no information at all.
Impact
Combined with the logging defect in #516 (errors serialize to {}), this leaves an operator with almost no way to diagnose a stuck or parked task from the dashboard — no timeline, and the log detail that does exist is empty.
Ask
Find where task transition events are supposed to be written (store.Transition, d.emit(events.Event{...}), etc.) versus what the timeline UI/API actually queries, and reconcile — either events aren't being persisted for these tasks, or the timeline endpoint is querying the wrong key/table.
Imported from beads archie-core-1786749700549-4-d2331d9d · GitHub #518 · type bug · priority P1 · created 2026-08-14 · closed 2026-08-15
## Problem
Every task's expanded timeline on `/tasks` reads "No events yet — This task has not recorded any transitions," regardless of status or how far the task progressed. Confirmed live across a `Working` task and multiple `Parked` tasks at different stages:
- `#1000000000000001` — Working, implement/baseline, 20+ minutes in
- `#1000000000000000` — Parked at implement/baseline (go build/VCS-stamp failure)
- `#445` — Parked at tdd/commit-push (git push permission error)
All three show the identical empty-timeline message. This isn't isolated to the currently-stuck task — the timeline feature appears non-functional for the whole deployment, which means the dashboard's per-task "what actually happened" view (the thing an operator reaches for first when a task needs attention) carries no information at all.
## Impact
Combined with the logging defect in #516 (errors serialize to `{}`), this leaves an operator with almost no way to diagnose a stuck or parked task from the dashboard — no timeline, and the log detail that does exist is empty.
## Ask
Find where task transition events are supposed to be written (`store.Transition`, `d.emit(events.Event{...})`, etc.) versus what the timeline UI/API actually queries, and reconcile — either events aren't being persisted for these tasks, or the timeline endpoint is querying the wrong key/table.
---
_Imported from beads `archie-core-1786749700549-4-d2331d9d` · GitHub #518 · type bug · priority P1 · created 2026-08-14 · closed 2026-08-15_
sam
added the highbug labels 2026-10-27 13:38:32 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Every task's expanded timeline on
/tasksreads "No events yet — This task has not recorded any transitions," regardless of status or how far the task progressed. Confirmed live across aWorkingtask and multipleParkedtasks at different stages:#1000000000000001— Working, implement/baseline, 20+ minutes in#1000000000000000— Parked at implement/baseline (go build/VCS-stamp failure)#445— Parked at tdd/commit-push (git push permission error)All three show the identical empty-timeline message. This isn't isolated to the currently-stuck task — the timeline feature appears non-functional for the whole deployment, which means the dashboard's per-task "what actually happened" view (the thing an operator reaches for first when a task needs attention) carries no information at all.
Impact
Combined with the logging defect in #516 (errors serialize to
{}), this leaves an operator with almost no way to diagnose a stuck or parked task from the dashboard — no timeline, and the log detail that does exist is empty.Ask
Find where task transition events are supposed to be written (
store.Transition,d.emit(events.Event{...}), etc.) versus what the timeline UI/API actually queries, and reconcile — either events aren't being persisted for these tasks, or the timeline endpoint is querying the wrong key/table.Imported from beads
archie-core-1786749700549-4-d2331d9d· GitHub #518 · type bug · priority P1 · created 2026-08-14 · closed 2026-08-15