FA-77189 / Calendar recurrence rules / Member archive

Pending alarms for a recurring timed series: ack key · case 04

Acknowledging an occurrence does not silence its alarm.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Occurrences start at dtstart + k*interval_hours for k < count. Each has one alarm at start + trigger_min minutes (negative means before the start). Occurrences whose start string (YYYY-MM-DDTHH:MM) is in acknowledged have no alarm. An alarm due at or before now is delivered at now if the occurrence has not started yet (start > now), otherwise dropped. Alarms due after now + horizon_hours are not scheduled. Return [occurrence_start, fire_time] pairs in series order.

Why this case matters

Recurring calendar series are expanded into concrete instances for display, reminders and conflict checks.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
ack and catch-up mix	`[["2024-02-01T09:00", "2024-02-01T08:00"], ["2024-02-01T12:00", "2024-02-01T08:00"], ["2024-02-01T15:00", "2024-02-01T11:00"], ["2024-02-01T18:00", "2024-02-01T14:00"]]`	`[["2024-02-01T09:00", "2024-02-01T08:00"], ["2024-02-01T15:00", "2024-02-01T11:00"], ["2024-02-01T18:00", "2024-02-01T14:00"]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.