示例
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
已验证示例 — golang google.golang.org/grpc v1.83.0: Configure gRPC-Go client and server receive message size limits to handle payloads exceeding the default 4MB…
sha256:2a0fa7cb93fe3b863e2520ac8f3cb87f14c3964a07c329047abda9a63073769d
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
go 1.26 linux x64 go 1.26 go go
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| 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 |
案例
HOW- 目标
- Configure gRPC-Go client and server receive message size limits to handle payloads exceeding the default 4MB limit
- 符号
-
- 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
- 环境
- go 1.26
- 创建时间
- 2026-08-17T11:54:02Z
契约
- 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.
文件
- NOTES.md
- csx.json
- go.mod
- go.sum
- message_size_test.go