You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The write receipt falls back to the ledger summary for the whole run when one write names no event, and no test covers delete_event or a non-UTC zone #948
Found by the single-seat Opus review of #941 (work of #935), finding listed in #935 (comment). Findings 2 and 10 (receipt half). When a single write in the run carries no event name the receipt in receipt-confirmation.ts uses the ledger summary of the whole run instead of building one named line per write, and receipt-confirmation.test.ts drives neither a delete_event write nor a user in a zone west of UTC.
Why (motivation)
A run with several writes should list each of them with its own event name and local time.
User impact
A person who created two events and deleted a third can receive one vague summary line instead of three precise ones, or a time shifted by their zone.
Cost of inaction
The vague receipt stays and a time-zone or delete regression would ship unnoticed.
Acceptance criteria
Test: three writes where one names no event give three lines, the unnamed one marked as such
Test: a delete_event write and a write for a user in a zone west of UTC render the local date and time
Screenshots
(none)
Deploy
Deployed: no
Links
(none)
Skipped gates
duplicate: searched incident, alert, watcher, validator, timeout, receipt; no ticket covers this
Activity