DangerousDragonfly8 Yes this is correct, we mixed-up the places we call these functions
DangerousDragonfly8 you can try to start the pipeline like this:pipe.start(step_task_completed_callback=callback)
where callback has the signature:def callback(pipeline, node, parameters): print(pipeline, node, parameters)
Note that even tho the parameter name is step_task_completed_callback
, it is actually ran before the task is started. This is actually a bug...
We will need to review the callbacks, but I think you can work with this for now...
SmugDolphin23 ok so pipe.start
with step_task_completed_callback
does indeed work because step_task_completed_callback
runs before the task is executed. step_task_created_callback
seems to run after the task is executed however so the naming seems to be reversed.
But the pre_execute_callback
from the pipe.add_function_step
needs to be fixed, it does run before the task is executed but the Node does not have any attributes set besides the name.
Hi DangerousDragonfly8 ! Sorry for the late reply. I'm taking a look and will come back to you shortly
No problem SmugDolphin23 and thank you. I am really quite stuck with this 😄