wahsmail commented on issue #15752:
URL: https://github.com/apache/airflow/issues/15752#issuecomment-846146800
Bump @jedcunningham
--
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
wahsmail commented on issue #15752:
URL: https://github.com/apache/airflow/issues/15752#issuecomment-844615103
Actually now I think I'd argue that
wahsmail commented on issue #15752:
URL: https://github.com/apache/airflow/issues/15752#issuecomment-844577901
So the choice is to either pass a localized datetime to croniter.get_next()
and *then* convert to UTC, or somehow mutate the schedule interval string such
that it gets the same
wahsmail commented on issue #15752:
URL: https://github.com/apache/airflow/issues/15752#issuecomment-844566053
Think I found something. In
[util.dates.py#L109](https://github.com/apache/airflow/blob/master/airflow/utils/dates.py#L109),
cron iter is returning a `datetime.datetime(2021, 4,
wahsmail commented on issue #15752:
URL: https://github.com/apache/airflow/issues/15752#issuecomment-844517963
Issue also persists in 2.0.2
This seems related: https://github.com/apache/airflow/issues/10112
Very annoying bug!
--
This is an automated message from the Apache