fritz-astronomer opened a new issue, #24324:
URL: https://github.com/apache/airflow/issues/24324

   ### Apache Airflow version
   
   2.3.2 (latest released)
   
   ### What happened
   
   Grid view for a Task Group (renders incorrectly)
   <img width="865" alt="image" 
src="https://user-images.githubusercontent.com/80706212/172630971-12ca3955-cc3c-4c47-ad56-2a7643551353.png";>
   
   Graph View for same Task Group (renders correctly)
   <img width="1168" alt="image" 
src="https://user-images.githubusercontent.com/80706212/172630694-cf29ef79-6b67-45e8-b15b-3196366f274c.png";>
   
   1) All historic DAG Runs for the task group are marked as "deferred" because 
the *current* DAG Run task group has a deferred task in it. It is observable in 
this screenshot that this is incorrect for all except the current DAG Run.
   
   2) Also there is a visual issue in rendering the bottom two task names of 
the task group - their names are cut off - `process_XXX_files_and_upload` 
turned into `s_XXX_files_and_upload`.
   
   ### What you think should happen instead
   
   1) Task group should report status based on it's DAG Run
   2) Task names should render correctly
   
   ### How to reproduce
   
   (assumption) Have a DAG with a Task Group and historical task runs in `2.3.2`
   
   ### Operating System
   
   Debian/Docker
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Astronomer
   
   ### Deployment details
   
   _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