Fix Dag Details start date bug #16206
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:UI
|
@uranusjr Couldn't request a review from you but here's the fix. |
|
How do I tell if the DAG has started in the proposed UI? I was imaginging there would be an indicator or a |
|
Updated. It will either show the
|
uranusjr
approved these changes
Jun 2, 2021
ryanahamilton
approved these changes
Jun 8, 2021
ashb
pushed a commit
that referenced
this pull request
Jun 22, 2021
* Only show Start Date when catchup=True * add catchup field to details * add started field for catchup=false dags (cherry picked from commit ebc03c6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix error of the start date being wrong when
catchup=Falseby hiding the Start Date and by addingcatchupas a field in Dag DetailsCloses #14299
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.