FAILURE MAP
← Case archive

FA-77153 / Calendar recurrence rules / Member archive

Monthly day 29-31 with OMIT/BACKWARD/FORWARD skip policy: forward target · case 03

FORWARD from February 31 lands on March 3 instead of March 1.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

FREQ=MONTHLY on a fixed monthday from the dtstart month. When the day does not exist in a month, skip decides: OMIT (also the default when skip is None) drops the month, BACKWARD uses the last day of the month, FORWARD uses the first day of the following month. February has 29 days in leap years. Instances before dtstart are dropped. Return the first count ISO dates.

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 fixtureActualExpectedOutcome
regression: 31st forward in common year["2023-01-31", "2023-03-03", "2023-03-31", "2023-05-01"]["2023-01-31", "2023-03-01", "2023-03-31", "2023-05-01"]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.

Sign in to the archive ↗