temporalio / temporalio/features
Confirm behavior of manually returning cancellation errors in all SDKs from workfows and activities
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
It is unclear how SDKs behave in the face of manually returned cancellation errors when a cancellation is not in progress. See https://github.com/temporalio/sdk-go/issues/686.
Describe the solution you'd like
- Make sure all SDKs do not try to send
RespondActivityTaskCanceledRequestto the server regardless of error type when there's not a cancellation requested from the server - Confirm that async complete activity still can be given cancellation error
Contributor guide
No contributing guide indexed for this repository
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
Start with the linked sdk-go issue 686 and the behavior described for workflows, activities, and async completion. Compare how each SDK handles manually returned cancellation errors when no server cancellation is active, then confirm the behavior across all SDKs, including async-completed activities.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100