Enrique
08/29/2022, 9:20 AMAnna Geller
08/29/2022, 11:07 AMtimeout_seconds
on your flow decorator, so if you convert this task to a subflow, you can already solve the issue this way.
Setting timeout on a task is a reasonable request - let's open an issue to investigate whether we can add that - I believe this would be hard to do with async and various distributed task runners like Dask or Ray, but Michael can estimate that best - you can follow up on the issue. Thanks for bringing this up and until then you can set a timeout on a subflow
@Marvin open "Consider adding timeout
to the task decorator"Marvin
08/29/2022, 11:08 AMEnrique
08/29/2022, 12:37 PMAnna Geller
08/29/2022, 1:52 PMEnrique
08/29/2022, 2:27 PMChris L.
09/16/2022, 3:54 AMtimeout
kwarg in the BaseTaskRunner
. But can't figure out where the timeout is being set? (https://github.com/PrefectHQ/prefect/blob/269e3678d03b820429f5e090a740b3d5e57058d9/src/prefect/task_runners.py#L132)
Wondering if this config can be changed globally? I have some long running tasks on Dask and it's timing out prematurely. Many thanks!future.result(timeout=s)
suggestion is it is (to my knowledge) a blocking operation in Dask (https://docs.dask.org/en/stable/futures.html#submit-tasks). I could use the client.gather
pattern with futures but it seems much easier to just configure timeout for all tasks.Anna Geller
09/16/2022, 11:25 AMChris L.
09/17/2022, 11:11 AM