temporalio / temporalio/features
[Feature Request] SDK should fail a workflow task if it receives non-ignorable events that it doesn't handle
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
We've recently added the worker_may_ignore flag to history events.
SDKs should start using this flag to enable adding new events that are safe to ignore by older SDKs.
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 worker_may_ignore flag in temporal/api/history/v1/message.proto and inspect the history-event handling paths covered by this repository’s compatibility tests. Define how SDKs should fail a workflow task for unhandled non-ignorable events, then add coverage showing the behavior across the relevant SDKs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100