temporalio / temporalio/temporal
Do not write repeated workflow task heartbeat to the history
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
A very long running local activity can lead to many repeated WorkflowTaskCompleted/Scheduled/Started events written to the history.
Describe the solution you'd like
Do not write these events if there are no commands included in WorkflowTaskCompleted and there are no new events.
We already do a similar "deduping" when processing constantly failing/timing out workflow tasks.
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
Start by tracing how WorkflowTaskCompleted, WorkflowTaskScheduled, and WorkflowTaskStarted events are written, then compare that path with the existing deduplication for constantly failing or timing-out workflow tasks. Done means repeated task events are omitted when WorkflowTaskCompleted has no commands and no new events are present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100