wolfier opened a new issue, #38098: URL: https://github.com/apache/airflow/issues/38098
### What do you see as an issue? The issue is that users are unaware of scheduling behaviour between transition of when [daylight saving time](https://en.wikipedia.org/wiki/Daylight_saving_time) is observed and when it is not. For daylight time saving observing timezones, at the cusp of when switching between when daylight saving time is **NOT** observed to when it is, there is an hour that does not exist. For example, 2 AM Central Time ("America/Chicago") does not exist on March 10th 2024. * `2024-03-10 7:59 UTC is 1:59 AM CT (CST)` * `2024-03-10 8:00 UTC is 3:00 AM CT (CDT)` * `2024-03-10 8:01 UTC is 3:01 AM CT (CDT)` For daylight time saving observing timezones, at the cusp of when switching between when daylight saving time is observed to when it is **NOT**, there is an hour that is repeated. For example, 1 AM Central Time ("America/Chicago") happens twice on November 3rd 2024. * `2024-11-03 6:59 UTC is 1:59 AM CT (CDT)` * `2024-11-03 7:00 UTC is 1:00 AM CT (CDT)` * `2024-11-03 7:01 UTC is 1:01 AM CT (CST)` * `2024-11-03 7:59 UTC is 1:59 AM CT (CST)` * `2024-11-03 8:00 UTC is 2:00 AM CT (CST)` * `2024-11-03 8:01 UTC is 2:01 AM CT (CST)` ### Solving the problem A description of the effects of these impacted schedule intervals in terms of dagrun creation as that is what drives task scheduling. Without a dagrun, there are no tasks. ### Anything else _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
