t4n1o edited a comment on issue #18541:
URL: https://github.com/apache/airflow/issues/18541#issuecomment-928440208
Would it help if I upgraded airflow to a newer version (2.14)?
The dag I'm running that caused this has `start_date` set to:
```
with DAG(
'Archives Mirror',
t4n1o edited a comment on issue #18541:
URL: https://github.com/apache/airflow/issues/18541#issuecomment-928440208
Would it help if I upgraded airflow to a newer version (2.14)?
The dag I'm running that caused this has `start_date` set to:
```
with DAG(
'Archives Mirror',
t4n1o edited a comment on issue #18541:
URL: https://github.com/apache/airflow/issues/18541#issuecomment-928440208
Would it help if I upgraded airflow to a newer version (2.14)?
The dag I'm running that caused this has `start_date` set to:
```
with DAG(
'Archives Mirror',
t4n1o edited a comment on issue #18541:
URL: https://github.com/apache/airflow/issues/18541#issuecomment-928440208
--
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 unsubs
t4n1o edited a comment on issue #18541:
URL: https://github.com/apache/airflow/issues/18541#issuecomment-940083883
Is there another way to avoid this error? (Like settings start_date to
something else?)
I can't manually apply a patch, my automated ansible install will overwrite
it anyti
