temporalio / temporalio/features
Treat Activity start as the first heartbeat time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Currently SDK will start throttling heartbeats after the first one is sent (first one called as part of activity code).
In some use cases this is not optimal where heartbeat throttling should be started at activity start.
This is especially critical for cloud customers where heartbeat is a billable action.
Ask is to treat Activity start as the first heartbeat time so first actual heartbeat sent would be at 4/5 of HeartbeatTimeout defined.
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
No file or test is named. Start by locating the activity-start handling and heartbeat-throttling behavior in the feature tests or SDK compatibility scenarios, then verify the expected timing. Done means throttling is anchored at activity start and the first actual heartbeat is sent at four-fifths of HeartbeatTimeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100