yuqili-newsbreak opened a new issue, #66959:
URL: https://github.com/apache/airflow/issues/66959

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   3.2
   
   ### What happened and how to reproduce it?
   
   ▎ Issue Description
   ▎
   ▎ In the DAG Calendar view (Hourly granularity, Total Runs), an hour cell 
whose run is in the FAILED state is rendered with the same solid green as 
success cells. The cell is
   ▎ visually indistinguishable from a successful hour — only the hover tooltip 
reveals the actual state.
   ▎
   ▎ The legend in this view only documents:
   ▎ - a green gradient (More / Less) for Total Runs,
   ▎ - Planned (gray),
   ▎ - Mixed (green/red split).
   ▎
   ▎ There is no swatch for queued. Hovering the green cell shows the tooltip 
Apr 08, 10:00 — 1 Queued even though the cell is colored as if it were a 
successful run.
   ▎
   ▎ Steps to reproduce
   ▎ 1. Open the Airflow 3.2 UI.
   ▎ 2. Open a DAG that has at least one hour-bucket whose run is in the queued 
state.
   ▎ 3. Navigate to the DAG → Calendar tab → granularity Hourly → metric Total 
Runs.
   ▎ 4. Hover over the cell containing the queued run — tooltip says N FAILED, 
but the cell is rendered solid green.
   
   ### What you think should happen instead?
   
   ▎ The queued state should have a visually distinct treatment in the Calendar 
heatmap (should be red) so the heatmap doesn't conflate
   ▎ failed runs with successes. Currently a cell holding only a failed run 
looks identical to a fully-successful hour, which is misleading.
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   None
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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