错误代码门户
GoogleGoogle APIs / gRPC错误代码

OUT_OF_RANGE

OUT OF RANGE

其他表示形式:11 · google.rpc.Code.OUT_OF_RANGE

代码 OUT_OF_RANGE · Google APIs / gRPC 报告的问题。

尝试的操作超出了有效范围。 例如,查找或读取文件末尾之后的内容。 与“INVALID_ARGUMENT”不同,此错误指示如果系统状态发生变化则可能会修复的问题。例如,如果要求读取不在 [0,2^32-1] 范围内的偏移量,32 位文件系统将生成“INVALID_ARGUMENT”,但如果要求读取超出当前文件大小的偏移量,则会生成“OUT_OF_RANGE”。 “FAILED_PRECONDITION”和“OUT_OF_RANGE”之间有相当多的重叠。 我们建议在应用时使用“OUT_OF_RANGE”(更具体的错误),以便迭代空间的调用者可以轻松查找“OUT_OF_RANGE”错误以检测何时完成。 HTTP 映射:400 错误请求

Google Translate · 此内容为自动翻译。技术术语及适用条件请以英文原文为准。

The operation was attempted past the valid range. E.g., seeking or reading past end-of-file. Unlike `INVALID_ARGUMENT`, this error indicates a problem that may be fixed if the system state changes. For example, a 32-bit file system will generate `INVALID_ARGUMENT` if asked to read at an offset that is not in the range [0,2^32-1], but it will generate `OUT_OF_RANGE` if asked to read from an offset past the current file size. There is a fair bit of overlap between `FAILED_PRECONDITION` and `OUT_OF_RANGE`. We recommend using `OUT_OF_RANGE` (the more specific error) when it applies so that callers who are iterating through a space can easily look for an `OUT_OF_RANGE` error to detect when they are done. HTTP Mapping: 400 Bad Request

故障排除与诊断链接

请先确认文档中的产品、版本及发生环境与当前情况一致。