temporalio / temporalio/sdk-python
[Feature Request] Implement proper behavior for `cancelled`, `uncancel`, and `cancelling` of activities and child workflows
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 241
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 55
Description
Describe the solution you'd like
Implement proper behavior for cancelled, uncancel, and cancelling of activities and child workflows. The behavior probably looks like:
cancelled- return true once it comes back as canceleduncancel- raise an (non-Temporal) exception saying that uncancel is not supportedcancelling- probably just works already
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the Python SDK for the implementations of activity and child-workflow cancellation, including the cancelled, uncancel, and cancelling APIs. Run the related cancellation tests, then verify that cancelled reflects the returned cancellation state, uncancel raises the intended exception, and existing cancelling behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100