temporalio / temporalio/temporal
Take additional factors into account for suggesting continue-as-new
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
The recently added mechanism for the server to suggest workflow continue-as-new is based on history event length and byte size.
Users can hit other limits such as number of signals received and scheduled activities, the server suggestion should take those factors into account to help users out.
See for reference: https://github.com/temporalio/api/blob/ae312b0724003957b96fb966e3fe25a02abaade4/temporal/api/history/v1/message.proto#L180
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 with the referenced temporal/api/history/v1/message.proto definition and trace the existing server mechanism that suggests continue-as-new. Determine how signal counts and scheduled-activity counts should be represented and evaluated; done means the suggestion accounts for those additional limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100