stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

CI browser journey loses active break state after corrupt-record recovery #1315

New Issue
Closed
opened 2026-08-23 17:39:22 +00:00 by timmy · 0 comments
timmy commented 2026-08-23 17:39:22 +00:00
Owner
Copy Link

Observed failure

The act_runner CI job browser-journey failed on 2026-08-23 at 17:26 UTC in tests/e2e/test_mobile_today_handoff_release.py::test_release_artifact_plans_hands_off_and_opens_next_mobile_issue.

After injecting and recovering a corrupt stackchain.today-sync localStorage record, #today-break-status becomes hidden/empty instead of retaining On break · resume in …. The same job reported 37 passing journeys and this one failure.

Acceptance criteria

  • Add/retain a failing regression test for active break state across corrupt-record recovery.
  • Preserve valid active break state while removing only unreadable records.
  • Browser journey and full unit suite pass under act_runner.

This is an automatically verified CI-health incident; avoid changing unrelated notification behavior.

## Observed failure The act_runner CI job `browser-journey` failed on 2026-08-23 at 17:26 UTC in `tests/e2e/test_mobile_today_handoff_release.py::test_release_artifact_plans_hands_off_and_opens_next_mobile_issue`. After injecting and recovering a corrupt `stackchain.today-sync` localStorage record, `#today-break-status` becomes hidden/empty instead of retaining `On break · resume in …`. The same job reported 37 passing journeys and this one failure. ## Acceptance criteria - Add/retain a failing regression test for active break state across corrupt-record recovery. - Preserve valid active break state while removing only unreadable records. - Browser journey and full unit suite pass under act_runner. This is an automatically verified CI-health incident; avoid changing unrelated notification behavior.
timmy self-assigned this 2026-08-23 19:26:06 +00:00
timmy closed this issue 2026-08-23 19:46:52 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1315
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?