temporalio / temporalio/features
Set larger maxInboundMetadataSize to accommodate unbounded Server error messages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
The server sometimes may generate large (and unbounded) error messages that don't fit into a standard 8Kb limit on headers in gRPC and HTTP/2.
See https://github.com/temporalio/temporal/issues/3284 for more details and Server side ticket to address it.
We already have a large limit on inbound messages from the server on SDK side, we should set maxInboundMetadataSize to a large value to accommodate such behavior of the Server and avoid cryptic messages for the user.
The proposed value is maxInboundMetadataSize = 4Mb
- https://github.com/temporalio/sdk-java/issues/1396
- GoSDK
- TS
- Python
- Core
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
Start in the GoSDK implementation of inbound metadata handling and locate the maxInboundMetadataSize configuration. Check the related behavior and history compatibility tests in this repository, then verify that the GoSDK accepts the proposed 4 MB limit without cryptic errors for large server error messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100