Calendar all-day Task Undo regression stopped with Done under pool contention #952

Open
opened 2026-10-02 21:42:17 +00:00 by kayg · 0 comments
Owner

The #655 real production browser regression stopped in all-day lane checkbox and Undo after the API and visible control reached Done. The macOS Meta+z shortcut did not produce an observed Todo within the 90-second poll. Exact output:

AssertionError: Task status remained done; expected todo
at taskStatus (.../calendar-taskday-655-657.mjs:41:9)
at tickAndUndo (.../calendar-taskday-655-657.mjs:322:8)

Run: cd apps/web && bun run test:e2e:taskday-655-657 --screenshots ../../artifacts/taskday-655-657 with the current production web build and the job's real server binary. Phone 390, light, macOS emulation. The same flow had already completed the timed Task cross-tab change and Undo.

The host was busy. Pool acquisition waits reached 25–29 seconds, and the server logged the job-worker restart and busy authentication database recorded in #951. The process stayed alive. This is not established as a product shortcut defect or a resource-only failure: the failed run did not retain the all-day Task writer trace. Commit 157aab195 adds that trace and the active target/modal state for the next run. The assertion remains unchanged.

The merge round must rerun this focused regression and establish whether Undo reaches its writer. Do not report the full focused browser suite as passing while this result is unresolved. This follow-up does not replace #655's exact workflow-status Undo fix and unit tests.

The #655 real production browser regression stopped in `all-day lane checkbox and Undo` after the API and visible control reached Done. The macOS `Meta+z` shortcut did not produce an observed Todo within the 90-second poll. Exact output: ``` AssertionError: Task status remained done; expected todo at taskStatus (.../calendar-taskday-655-657.mjs:41:9) at tickAndUndo (.../calendar-taskday-655-657.mjs:322:8) ``` Run: `cd apps/web && bun run test:e2e:taskday-655-657 --screenshots ../../artifacts/taskday-655-657` with the current production web build and the job's real server binary. Phone 390, light, macOS emulation. The same flow had already completed the timed Task cross-tab change and Undo. The host was busy. Pool acquisition waits reached 25–29 seconds, and the server logged the job-worker restart and busy authentication database recorded in #951. The process stayed alive. This is not established as a product shortcut defect or a resource-only failure: the failed run did not retain the all-day Task writer trace. Commit 157aab195 adds that trace and the active target/modal state for the next run. The assertion remains unchanged. The merge round must rerun this focused regression and establish whether Undo reaches its writer. Do not report the full focused browser suite as passing while this result is unresolved. This follow-up does not replace #655's exact workflow-status Undo fix and unit tests.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
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
kayg/calternal#952
No description provided.