gRPC 3 INVALID_ARGUMENT vs 11 OUT_OF_RANGE
Both gRPC 3 (INVALID_ARGUMENT) and 11 (OUT_OF_RANGE) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 11 means that the operation was attempted past the valid range. For example, seeking or reading past the end of a file.
描述
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
何时出现
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
如何修复
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
描述
The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
何时出现
A pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
如何修复
Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.
主要区别
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
You encounter 11 when a pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
何时使用哪个
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 11 (OUT_OF_RANGE): Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.