Skip to content

Side-effect-free way of checking on task status #663

@ericmjonas

Description

@ericmjonas

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:

  1. Side-effect-free way of querying task status
  2. better documentation that the existing operations are NOT side-effect free (note for people used to building distributed systems, this can be quite surprising!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions