Geert
07/10/2023, 2:07 PMwith_overrides(_node_name_=f"{variable}-some-task")
to set a less cryptic name for my dynamic task (to have {variable}-some-task
show in the UI instead of d1-n-dn0
), and that works on first glance, but they get changed when the workload starts running; and stay that way after completion. Is this a bug or expected behaviour? Any way to get the name to stay?Yee
Geert
07/11/2023, 6:55 AMYee
futures.pb
file (it should be in the same place where you normally find the outputs.pb
) for the dynamic task?Geert
07/12/2023, 12:29 PMfutures.pb
contains some sensitive credentials, let me make a version that can be shared štask_some_other_task
in this example), the issue occurs.
from flytekit import Resources, WorkflowFailurePolicy, dynamic, task, workflow
@task(
limits=Resources(mem="500Mi"),
)
def some_task(
val: str,
):
print(val)
@dynamic(limits=Resources(mem="500Mi"))
def base_workflow():
# set up task promises
for val in ["one", "two", "three"]:
task_some_task = some_task(
val=val,
).with_overrides(node_name=f"{val}-some-task")
task_some_other_task = some_task(
val=val,
).with_overrides(node_name=f"{val}-some-other-task")
task_some_task >> task_some_other_task
@workflow( failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE,
)
def wf():
base_workflow()
task_some_task
completes, the names of subsequent tasks get updated to random string: