You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/12/01 18:30:51 UTC

[GitHub] [airflow] ferruzzi commented on issue #19801: Airflow scheduler crashed with TypeError: '>=' not supported between instances of 'datetime.datetime' and 'NoneType'

ferruzzi commented on issue #19801:
URL: https://github.com/apache/airflow/issues/19801#issuecomment-983941612


   > So the value was unintended? In that case I guess we could just invent an arbitrary cap to `poke_interval` and just make the DAG error out on parse. It does not need to be that precise either.
   
   That would be an easy check in the base sensor, I can get that one done.  Should we implement a cap to dag schedule-interval as well?


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org