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
Per a conversation on slack, there is no current side-effect-free way of checking on task status. This makes it difficult as an end user to write correct, reliable code, especially when get_result() can potentially propagate a task-internal exception (or raise a funcx/globus/network-related exception). And when exceptions occur while getting tasks, the task IDs can also be lost depending on how people have written their code.
So my request would be:
Side-effect-free way of querying task status
better documentation that the existing operations are NOT side-effect free (note for people used to building distributed systems, this can be quite surprising!)
The text was updated successfully, but these errors were encountered:
Per a conversation on slack, there is no current side-effect-free way of checking on task status. This makes it difficult as an end user to write correct, reliable code, especially when
get_result()
can potentially propagate a task-internal exception (or raise a funcx/globus/network-related exception). And when exceptions occur while getting tasks, the task IDs can also be lost depending on how people have written their code.So my request would be:
The text was updated successfully, but these errors were encountered: