-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
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
Task Group: Node order changes after collapse #13044
Comments
CC @yuqian90 |
Thanks @JCoder01, as I understand this is not a "real bug" but just an unpleasant UX, right? |
@turbaszek Yeah, there is nothing wrong with the functionality. It's just a tad annoying when things move around. |
In fact, this isn't an issue for I can understand the pain. However, this issue needs to be addressed in the dependent package Dagre. I think this is the open issue upstream: dagrejs/dagre#189 Unfortunately it doesn't look like they are addressing it any time soon. Hopefully someone can come up with a workaround. |
Could some test this on Rc3 -- I don't see it there. If you do see it, please give me a reproduction test case. |
@ashb Just installed RC3 and see the same. The behavior is evident on that example_task_group dag. |
I wonder if I don't see it cos I use Firefox |
I don't know, I tried Firefox on both windows and linux and the same thing happens. |
@bbovenzi Can you take a look at this one when you have time please |
dagre still has not been updated. If someone wants to fork that library or add logic to remember the order, feel free to open a PR. But I will not be focusing on this as we will use a different graphing library in AIP-38. |
Hi @bbovenzi , just curious, what graphing library are we switching to in AIP-38? I think it makes sense to start thinking about how to implement Graph View and Tree View using that new library. |
@yuqian90 I'm still looking into it, so I'm open to suggestions. We can certainly bring those updates into the current UI when it's well tested. |
Just tested again in the new graph view. Group children appear to maintain their order. |
Apache Airflow version: 2.0.0rc1
Kubernetes version (if you are using kubernetes) (use
kubectl version
):Environment:
uname -a
):What happened:
The order of the nodes changes when expanding and collapsing task groups:
Before:
After expanding task group and collapsing:
What you expected to happen:
node order to be consistent
How to reproduce it:
Create a DAG with multiple task groups.
expand the top group
collapse the top group
observe is is now at the end.
Anything else we need to know:
happens every time.
The text was updated successfully, but these errors were encountered: