Revert "AIP-86: Add deadline to DagResponse (#51698)"
#53616
Merged
+3
−217
Conversation
This file contains hidden or 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
This reverts commit 7c31bb5
ferruzzi
requested review from
bbovenzi,
pierrejeambrun,
ryanahamilton,
jscheffl,
shubhamraj-git,
bugraoz93,
kaxil,
potiuk,
ephraimbuddy,
rawwar and
jason810496
as code owners
boring-cyborg
bot
added
area:airflow-ctl
area:API
ramitkataria
approved these changes
Jul 22, 2025
vincbeck
approved these changes
Jul 22, 2025
o-nikolas
deleted the
ferruzzi/deadlines/08-revert-Add-deadline-to-DagResponse
branch
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.
This reverts commit 7c31bb5. I'm positive, but I think the intent was to make the deadlines info available to the frontend UI. I dropped a message on their PR over a month ago pointing out that it causes an exception and doesn't work and they haven't replied. We can worry about adding UI elements later, I think we should just revert the breaking change for now.
((Replaces #53613 which had an issue, sorry about the multiple notifications to those who get auto-tagged for review.))
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.