-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix visible DagRun doesn't point to the same dag run id #38365
Conversation
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me this looks good but I am only 90% certain if this is "right". @bbovenzi Can you double check before merge?
As stated by @nivdror, displaying a DAG RUN date different from the dag run id may cause confusion to users. I fixed this by changing the default displayed date to the Interval Start Date instead of Interval End Date.
Gentle bump @bbovenzi. I do wonder if both places should use logical_date instead though. |
Let's go for logical date then |
Is there anything I should add or change? |
Is there anything I could contribute to help merge this Pull Request? |
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
) As stated by @nivdror, displaying a DAG RUN date different from the dag run id may cause confusion to users. I fixed this by changing the default displayed date to the Interval Start Date instead of Interval End Date. Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> (cherry picked from commit 4dce745)
) As stated by @nivdror, displaying a DAG RUN date different from the dag run id may cause confusion to users. I fixed this by changing the default displayed date to the Interval Start Date instead of Interval End Date. Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> (cherry picked from commit 4dce745)
apache#38365) As stated by @nivdror, displaying a DAG RUN date different from the dag run id may cause confusion to users. I fixed this by changing the default displayed date to the Interval Start Date instead of Interval End Date. Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
As stated by @nivdror, displaying a DAG RUN date different from the dag run id may cause confusion to users. I fixed this by changing the default displayed date to the Interval Start Date instead of Interval End Date.
closes: #35946