28 ms·
This is a pitfall. I’m working on something similar (internal solution) and dynamic task graph bites back hard very quickly. Domain I’m working on is very pron
by xlii 2y ago
This is a pitfall. I’m working on something similar (internal solution) and dynamic task graph bites back hard very quickly.
Domain I’m working on is very prone to a failure so having simple visualization/interaction (e.g. click to inspect/retry) is an important feature.
For that task graph needs to be resolved and static before actual execution phase. Nothing prevents multi-loop resolution (i.e. task graph which result is a task graph). Just make sure artifact sits in-between.
- noneback 2y agoTotally agree. Dependency handling is quite tricky in a changing Dynamic Graph.