temporalio / temporalio/features
Standardize unregistered Activity Type behavior
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
What does each SDK do when a Worker gets an Activity Task for an unregistered Activity Type, and what do we want to happen?
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 by comparing how each SDK handles a Worker receiving an Activity Task for an unregistered Activity Type. No files or tests are named; done requires an agreed behavior across SDKs and corresponding compatibility coverage.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100