We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.3.2 (latest released)
For latest version (2.3.2) Airflow, on grid view UI all the task cells in the same row are showing same state(latest state):
In the response json of grid_data API we can see all the instances have the same data except run_id.
grid_data
run_id
I think the children were same for all the instances here, which caused the problem: https://github.com/apache/airflow/blob/2.3.2/airflow/www/views.py#L300
children
Each task cell should show correct data.
No response
Ubuntu 19.10
Other 3rd-party Helm chart
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Be sure to follow the issue template!
Sorry, something went wrong.
Duplicate of #24410 and fixed in #24327
No branches or pull requests
Apache Airflow version
2.3.2 (latest released)
What happened
For latest version (2.3.2) Airflow, on grid view UI all the task cells in the same row are showing same state(latest state):
In the response json of
grid_data
API we can see all the instances have the same data exceptrun_id
.I think the
children
were same for all the instances here, which caused the problem:https://github.com/apache/airflow/blob/2.3.2/airflow/www/views.py#L300
What you think should happen instead
Each task cell should show correct data.
How to reproduce
No response
Operating System
Ubuntu 19.10
Versions of Apache Airflow Providers
No response
Deployment
Other 3rd-party Helm chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: