FA-77199 / Calendar recurrence rules / Member archive

UNTIL value forms and COUNT/UNTIL precedence for timed series: utc until · case 04

A UTC UNTIL in a zone east of UTC cuts off the last local instance.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

A daily-interval timed series in a fixed local offset (offset_min east of UTC). until may be None, a date (inclusive through the end of that local day, i.e. 23:59), a local date-time (inclusive), or a UTC date-time ending in Z (converted to local by adding offset_min). count may be None; count 0 means no instances. When both are given the series stops at whichever limit is reached first. Unbounded series are capped at 40 instances. Return ISO local date-times.

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
utc until east offset	`["2024-01-01T09:00", "2024-01-02T09:00"]`	`["2024-01-01T09:00", "2024-01-02T09:00", "2024-01-03T09: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.