temporalio / temporalio/temporal
Single active timer task per workflow
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Currently, we have multiple timer tasks per one workflow:
- one for user timers
- one for activities
- one for workflow task
- one for workflow execution
Ideally, we should only create one next timer for any kind, and create next in line after current one fires.
Also need the ability to delete timer if new timer created is earlier than current one.
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
The issue names no files, tests, or entry points. Start by locating where timer tasks are created and scheduled for user timers, activities, workflow tasks, and workflow execution; map how the next timer is selected and how earlier timers can replace the current one. Done means one active timer per workflow, with the next timer created after it fires and an earlier new timer able to delete or replace the current timer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100