java-operator-sdk
java-operator-sdk copied to clipboard
Workflow Cycle Detection - Explicit Cycle Logging
Workflows are essentially acyclic, detecting cycles is already implemented in PR: https://github.com/java-operator-sdk/java-operator-sdk/pull/1257
However this approach does not log the detected cycle - just logs that "there is a cycle" - thus nodes involved in the cycle. It would improve the developer experience if the cycle is clearly logged.
IMO this is a low priority issue since its not hard to find the cycles just by looking on the declaration of the workflow. It is not that we are solving a very complex bean structure across the code, it is expected to be relatively simple DAG declared in very transparent way in one place.
Agreed, while my inner geek would like super neat graph algorithms and optimisations, we probably don't need them at this point.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.
This issue was closed because it has been stalled for 14 days with no activity.