Open datafibers opened 6 years ago
We detect that when adding new connect, some existing running connect will become UNASSIGNED within a short time from RUNNING, then it goes back to normal. In this case, we do not want to show it (disable connect change detection) if the coming status is UNASSIGNED when status in the repository is RUNNING. @SchubertZhu This is ready for testing as well.
When we add a connect/transform, other running tasks becomes UNASSIGNED. We need to investigate this to see if this is a code issue or software issue