3 ms·
Read the example code, have a sinking feeling that is not taken from a real tested example. Either there are multiple unexplained symbols or teh code does not a
by pierrebai 2y ago
Read the example code, have a sinking feeling that is not taken from a real tested example. Either there are multiple unexplained symbols or teh code does not actually run.
For example, in "Implementing a Workflow" the execute_activity refers to Purchaser.purchase, which is not declared anywhere.
If the execute_activity times-out after 1 minutes, the status does not seem to be updated anywhere.
In "Running a Worker", do_purchaser is passed as an activity, without explanation. (I guess I'd need to read the fundamental Temporal docs?)
- kodablah 2y agoYes, it has undergone revisions since which caused function name mismatch (EDIT: fixed). The execute_activity there uses start_to_close_timeout which is per attempt and will retry forever by default (customizable). This is more of a primer on the Python part of Temporal rather than an explanation of all Temporal concepts in depth. Definitely would recommend reading the fundamental docs at https://docs.temporal.io/encyclopedia/ https://docs.temporal.io/encyclopedia/. For more exact samples, see https://github.com/temporalio/samples-python https://github.com/temporalio/samples-python.