Sample
google.golang.org/grpc v1.83.0: Configure gRPC-Go client and server receive message size limits to handle payloads exceeding the default 4MB limit
Verified sample for golang google.golang.org/grpc v1.83.0: Configure gRPC-Go client and server receive message size limits to handle payloads exceeding the…
sha256:2a0fa7cb93fe3b863e2520ac8f3cb87f14c3964a07c329047abda9a63073769d
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
go 1.26 linux x64 go 1.26 go go
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-17 |
| go 1.26 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-18 |
Case
HOW- Goal
- Configure gRPC-Go client and server receive message size limits to handle payloads exceeding the default 4MB limit
- Symbols
-
- google.golang.org/grpc.NewServer
- google.golang.org/grpc.NewClient
- google.golang.org/grpc.MaxRecvMsgSize
- google.golang.org/grpc.MaxCallRecvMsgSize
- google.golang.org/grpc.MaxCallSendMsgSize
- google.golang.org/grpc.WithDefaultCallOptions
- google.golang.org/grpc.WithContextDialer
- google.golang.org/grpc.WithTransportCredentials
- google.golang.org/grpc.ClientConn.Invoke
- google.golang.org/grpc/status.Code
- google.golang.org/grpc/codes.ResourceExhausted
- Environment
- go 1.26
- Created
- 2026-08-17T11:54:02Z
Contract
- When a gRPC server returns a 5MB payload to a client with default options, the server transmits it without error but the client fails to decode the response with status code ResourceExhausted because the default client-side receive limit is 4MB.
- Configuring grpc.WithDefaultCallOptions(grpc.MaxCallSendMsgSize(10*1024*1024)) on the client does not permit receiving 5MB responses and still results in ResourceExhausted.
- Configuring grpc.WithDefaultCallOptions(grpc.MaxCallRecvMsgSize(10*1024*1024)) or passing grpc.MaxCallRecvMsgSize to Invoke allows the client to successfully receive the 5MB response.
- Sending a 5MB request from a client to a server with default options causes the server to reject the incoming message with status code ResourceExhausted unless the server is configured with grpc.MaxRecvMsgSize.
Files
- NOTES.md
- csx.json
- go.mod
- go.sum
- message_size_test.go