temporalio / temporalio/temporal
How to ensure that activities belonging to the same workflow can be prioritized and executed to avoid hunger when a batch of tasks is initiated for a workflow containing multiple activities.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
How to ensure that activities belonging to the same workflow can be prioritized and executed to avoid hunger when a batch of tasks is initiated for a workflow containing multiple activities.
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 the workflow activity scheduling and task-batching paths, then define how activities from one workflow should be prioritized and how hunger avoidance can be verified under a multi-activity batch.
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
- Needs clarification
- Newbie friendliness
- 20/100