shai-ikko commented on issue #40841:
URL: https://github.com/apache/airflow/issues/40841#issuecomment-2256026832
Hi, I've looked a little more into documentation and code.
Since I think the `start_date`/`execution_date` comparison is utterly wrong,
I've tried just commenting it out. I
omkar-foss commented on issue #40841:
URL: https://github.com/apache/airflow/issues/40841#issuecomment-2255245212
Hey @shai-ikko, good to hear from you. Apologies on my delayed response here.
So in [this PR](https://github.com/apache/airflow/pull/40963), the check
I've added - to chec
shai-ikko commented on issue #40841:
URL: https://github.com/apache/airflow/issues/40841#issuecomment-2247433686
Hi @omkar-foss , thanks for this!
Indeed, I've checked again, and the `start_date` on the DAG itself is
updated -- so it does not represent "this is when this DAG came into
omkar-foss commented on issue #40841:
URL: https://github.com/apache/airflow/issues/40841#issuecomment-2245709461
Hey @shai-ikko, based on the steps you provided above, I was able to
reproduce this issue in my local Airflow.
I tried out your sensor DAG and observed that the dep check
shai-ikko commented on issue #40841:
URL: https://github.com/apache/airflow/issues/40841#issuecomment-2236365767
There may have been some misunderstanding here - I am willing, in principle,
to submit a PR, but I have no clue about the fix. The bug submission form
promised that guidance may
boring-cyborg[bot] commented on issue #40841:
URL: https://github.com/apache/airflow/issues/40841#issuecomment-2233573341
Thanks for opening your first issue here! Be sure to follow the issue
template! If you are willing to raise PR to address this issue please do so, no
need to wait for ap
shai-ikko opened a new issue, #40841:
URL: https://github.com/apache/airflow/issues/40841
### Apache Airflow version
main (development)
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
Airflow has two `start_date` fields
