Jay Ganbat04/04/2022, 6:17 PM
that calls another
regular python task(T1)
without it being dynamic; T2 is a very simple function that runs quickly. I did not want to make T1 dynamic since i didnt wanna add overhead of launching pod for T2. Also I am using T2 in a workflow as a regular python task. My question is
regular python task(T2)
or is it fine to call regular task from another regular task. i could create a regular python function and call that from T1 but then i need to create another wrapper for T2 which just calls the regular function and i wanted to avoid that extra stuff. From this page https://docs.flyte.org/projects/cookbook/en/latest/auto/core/flyte_basics/task.html#sphx-glr-auto-core-flyte-basics-task-py i read that
is it a correct way to use it?
maybe i took this statement a bit too liberally
You can execute a Flyte task as any normal function.
error when trying to execute locally.
Promise object is not iterable
Jay Ganbat04/04/2022, 6:59 PM
support local execution? I am getting the similar Promise error
TypeError: Failed to convert return value for var o0 for function balrog_pipeline.workflows.primer_qc.process_expected_primer_qc_workflow.mapper_calculate_spike_in_metrics_in_fastq_dir_2 with error <class 'TypeError'>: No automatic conversion found from type <class 'flytekit.core.promise.Promise'> to FlyteFile.Supported (os.PathLike, str, Flytefile)
Jay Ganbat04/04/2022, 11:18 PM
Jay Ganbat04/04/2022, 11:25 PM