temporalio / temporalio/sdk-java
[Feature Request] Improving replay issue for Timers
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Currently timers create a different execution history if timer / sleep duration is <=0 or > 0. A number of users a running into problems on internal workflow replay for this. It would be nice to add some checks to reduce the number of non-deterministic errors timer duration can lead to.
Contributor guide
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
No files, tests, or entry points are named. Start by locating timer and sleep handling and their replay paths in the Java SDK; define done as checks that prevent differing histories for non-positive versus positive durations, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100