temporalio / temporalio/features
Decide/apply/clarify ambiguous failure behavior in signals and workflows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Related to #481. Currently exceptions in signal handlers are treated as if they were thrown in the main workflow function. But what happens when workflow function and signal handler both throw an exception in the same task? Which takes precedence?
The task is to confirm how each SDK does it today, if it will change with #481, and what if anything we want to do about it.
Per-SDK Tickets
TODO - pending outcome
- Go -
- Java -
- Core - N/A
- TypeScript -
- Python -
- .NET -
- PHP -
- Temporal CLI - N/A
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
Compare how the listed SDKs handle simultaneous exceptions from the workflow function and a signal handler, and check the impact of #481. Record the current precedence behavior for Java, TypeScript, Python, .NET, and PHP, then determine whether any behavior should change. Done means the per-SDK tickets are resolved with an agreed outcome; Go and Core are already marked complete or not applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, php, python, typescript
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100