distributed 2021.10.0

ParametersReturns
recreate_task_locally(self, future)

This operation should be performed after a future (result of gather , compute , etc) comes back with a status other than "pending". Cases where you might want to debug a successfully completed future could include a calculation that returns an unexpected results. A common debugging process might include running the task locally in debug mode, with pdb.runcall .

Parameters

future : future

The same thing as was given to gather .

Returns

Any; will return the result of the task future.

For any calculation, whether it succeeded or failed, perform the task locally for debugging.

Examples

This example is valid syntax, but we were not able to check execution
>>> import pdb                                    # doctest: +SKIP
... future = c.submit(div, 1, 1) # doctest: +SKIP
... future.status # doctest: +SKIP 'finished'
This example is valid syntax, but we were not able to check execution
>>> pdb.runcall(c.recreate_task_locally, future)  # doctest: +SKIP
See :

Local connectivity graph

Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.

Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)

SVG is more flexible but power hungry; and does not scale well to 50 + nodes.

All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them


File: /distributed/recreate_tasks.py#113
type: <class 'function'>
Commit: