timkpaine commented on PR #30083: URL: https://github.com/apache/airflow/pull/30083#issuecomment-1472826621
> changing how the cron syntax works *fixing the cron parsing. If your cron says "* 9,10" but once a year runs on 10,11 and 8,10, it's not "changing how the syntax works", it's fixing a long-standing bug (possibly breaking users that rely on that bug). It also isn't an undoable change: if you want absolute time, use an absolute time timezone like UTC. I don't think a separate timetable is necessary, and certainly having the default timetable when using cron be a broken one is not preferable. But maybe a flag on the existing cron timetable is acceptable? Something obvious like `adjust_for_dst` and possibly even a warning if you have a schedule that will be affected and don't set this flag. Most existing workarounds that I'm familiar with involve running +/- an hour and checking the real time to see if you should run, which would continue to work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
