temporalio / temporalio/features
Support an option to disable "Close" timeouts for indefinitely running Activities
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Some use cases involve creating an Activity meant to run indefinitely until canceled. However, the Java SDK doesn't offer a first-class way to disable the StartToClose/ScheduleToClose timeouts.
There are options such as ChronoUnit/FOREVER, but using them is somewhat awkward and throws an ArithmeticException.
The feature request is to provide a first-class way to disable the timeout as an option. This could be supplied as a convenient Duration "MAX" type that is Temporal compatible or some option that allows *Close options to remain unspecified.
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 reviewing the Java SDK's Activity timeout options, especially StartToClose and ScheduleToClose, and how ChronoUnit.FOREVER and Duration are handled. Compare the proposed Duration MAX approach with leaving the Close options unspecified, then define behavior that disables the timeouts without ArithmeticException and verify compatibility with indefinitely running Activities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100