You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The timeout handlers in prefect.utilities.executors generally work well. However, I've stumbled across an edge case in which they incorrectly signify a timeout occurred, when clearly one didn't occur:
For the multiprocessing timeout handler, this might be unavoidable. The best we could do is use multiprocess instead of multiprocessing, which uses the dill serializer instead of pickle, but either way prefect.context isn't handled well. It appears that customizing the serializer isn't really an exposed option right now, otherwise we could use cloudpickle. :/
The timeout handlers in
prefect.utilities.executors
generally work well. However, I've stumbled across an edge case in which they incorrectly signify a timeout occurred, when clearly one didn't occur:The timeout handlers work by placing objects into Queues, so for some reason it seems that certain objects disappear from the Queue.
This is almost certainly related to the fact that
context
isthread.local
as seen by the following example:I think returning objects from context is a reasonable enough thing that we should either find a way to detect this or raise a more informative error.
The text was updated successfully, but these errors were encountered: