imrichardwu opened a new pull request, #62195:
URL: https://github.com/apache/airflow/pull/62195

    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   This PR adds frontend UI indicators and a new Deadlines tab to improve 
observability of DAG runs.
   
   ## Changes included
   
   ### Grid view indicators
   
   - Adds a failed-run indicator rendered above the duration bar for runs in 
the failed state.
   - Adds a missed-deadline indicator rendered above the duration bar for runs 
with at least one
     missed deadline.
   - When both apply, icons are stacked vertically with dynamic offsets to 
avoid overlap.
   - Icons are clickable:
     - Failed icon navigates to the task-instances (run detail) view.
     - Deadline icon navigates to the new Deadlines tab.
   
   ### Icons and rendering
   
   - Adds FailedIcon and DeadlineIcon Chakra createIcon components for React 
usage.
   - Adds a Chart.js canvas plugin to render failed-run indicators inside 
DurationChart, since
     Chart.js operates on a canvas element.
   
   ### Deadlines tab
   
   - Adds a new Deadlines tab to the Run detail view.
   - Displays a sortable, filterable table of deadlines for a DAG run.
   - Columns include:
     - Alert name
     - Deadline time
     - Status (Missed / On Track)
     - Created at
     - Description
   - Includes a checkbox to filter to missed deadlines only.
   
   ### Routing
   
   - Updates the Run detail router to include the new deadlines route.
   
   ## Notes
   
   - This PR depends on the backend API changes that expose deadline 
information.
   - No backend or OpenAPI changes are included in this PR.
   - Relies on this [pr](https://github.com/apache/airflow/pull/62189)
   
   I am in the MLH Fellowship and working with @ferruzzi, so there are no 
GitHub issues for this.
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to