temporalio / temporalio/features
[Feature Request] Consider TLS handshake failures as worker-fatal errors
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
On any TLS failure do the normal retry we should do for all worker poll calls, then consider it a fatal error to fail the worker. Do not retry TLS handshake issues forever. This means TLS handshake failures probably need to be differentiated from normal (sometimes spurious) connection failures.
Per-SDK Tickets
- Go - TODO
- Java - TODO
- Core - TODO
- TypeScript - N/A
- Python - N/A
- .NET - N/A
- PHP - N/A
- 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
The issue names no files or tests. Start by tracing worker poll retry and TLS handshake error handling in the Go and Java SDKs, then compare their behavior with the requested fatal-worker outcome. Done means the Go and Java checklist items have an agreed implementation and coverage for retrying once before treating a TLS handshake failure as fatal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100