temporalio / temporalio/features
[Feature Request] SDKs should not fatal the worker on any error without a retry period
Nobody has claimed this yet.
- 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.
Today Go (and probably Java) will fatal error the worker if server returns InvalidArgument or NamespaceNotFound. These were originally assumed to be unrecoverable errors but we are now understanding at least InvalidArgument is recoverable (server sends InvalidArgument if the gRPC deadline is too close to now).
Describe the solution you'd like
Every SDK should react the same to seeing a worker error. They should probably mimic core in that they retry for so long, even fatal ones, before actually being fatal.
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 the Go and Java SDK workers handle InvalidArgument and NamespaceNotFound, then compare that behavior with the core retry behavior described in the issue. Done means every SDK handles worker errors consistently, retrying for a defined period before treating them as fatal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc, java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100