temporalio / temporalio/features
[Feature Request] Work around gRPC message size limit for task completion
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Task completion of many medium-input-payload activities in one task will cause issue with gRPC max message size. Temporal team is discussing solutions, the most common of which is likely having support for multi-RPC partial task completion.
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 files, tests, or entry points are named. Begin by clarifying the proposed multi-RPC partial task-completion contract with the Temporal team, then identify the affected task-completion RPC and compatibility tests; done means large task completions no longer hit the gRPC message-size limit while existing behavior remains compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100