nclaeys commented on issue #35272: URL: https://github.com/apache/airflow/issues/35272#issuecomment-1822707361
I just wanted to pitch in and make sure that a fix is provided for this issue. I see a long discussion on PR: #30083 on whether it is breaking existing functionality. On this I have 2 thoughts: - If I use a cron expression "0 9 * * *", I expect it always to run at 9 if I specify my local timezone irregardless of whether we switch from DST. Otherwise the dag code does not describe what the behavior is. - The more pressing is not that the schedule is 1 hour off but that it completely breaks the scheduling in some scenarios (as it pings between 1 hour when transitioning DST). This is really problematic and I just encountered this issue just again for one of our customers. Please make sure that whatever solution you choose, calculating the next dagrun works across DST transitions when using a non UTC timezone. -- 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]
