ID | NAME | TEXT | 大意 |
---|---|---|---|
0 | OK | 成功 | |
1 | CANCELLED | The operation was cancelled (typically by the caller). | 被取消 |
2 | UNKNOWN | Unknown error. An example of where this error may be returned is if a Status value received from another address space belongs to an error-space that is not known in this address space. Also errors raised by APIs that do not return enough error information may be converted to this error. | 比如:下层API没返给足够的信息,用这个。 |
3 | INVALID_ARGUMENT | Client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name). | 参数错误 |
4 | DEADLINE_EXCEEDED | Deadline expired before operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire. | 比如延迟拿到结果的查询请求。 |
5 | NOT_FOUND | Some requested entity (e.g., file or directory) was not found. For privacy reasons, this code may be returned when the client does not have the access right to the entity. | 没找到文件或没找到 |
6 | ALREADY_EXISTS | Some entity that we attempted to create (e.g., file or directory) already exists. | 已经存在 |
7 | PERMISSION_DENIED | The caller does not have permission to execute the specified operation. PERMISSION_DENIED must not be used for rejections caused by exhausting some resource (use RESOURCE_EXHAUSTED instead for those errors). PERMISSION_DENIED must not be used if the caller can not be identified (use UNAUTHENTICATED instead for those errors). | 权限问题 |
8 | RESOURCE_EXHAUSTED | Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space. | 资源用完了。 |
9 | FAILED_PRECONDITION | Operation was rejected because the system is not in a state required for the operation’s execution. For example, directory to be deleted may be non-empty, an rmdir operation is applied to a non-directory, etc. A litmus test that may help a service implementor in deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE: (a) Use UNAVAILABLE if the client can retry just the failing call. (b) Use ABORTED if the client should retry at a higher-level (e.g., restarting a read-modify-write sequence). © Use FAILED_PRECONDITION if the client should not retry until the system state has been explicitly fixed. E.g., if an “rmdir” fails because the directory is non-empty, FAILED_PRECONDITION should be returned since the client should not retry unless they have first fixed up the directory by deleting files from it. (d) Use FAILED_PRECONDITION if the client performs conditional REST Get/Update/Delete on a resource and the resource on the server does not match the condition. E.g., conflicting read-modify-write on the same resource. | |
10 | ABORTED | The operation was aborted, typically due to a concurrency issue like sequencer check failures, transaction aborts, etc. See litmus test above for deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE. | |
11 | OUT_OF_RANGE | Operation tried to iterate past the valid input 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. | 越界,数据不足 |
12 | UNIMPLEMENTED | Operation is not implemented or not supported/enabled in this service. | 访问了基类的某个派生类才能调用的函数。 |
13 | INTERNAL | Internal errors. Means some invariant expected by the underlying system has been broken. If you see one of these errors, something is very broken. | 底层系统错误。 |
14 | UNAVAILABLE | The service is currently unavailable. This is a most likely a transient condition and may be corrected by retrying with a backoff. See litmus test above for deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE. | 访问的资源暂时不可用,有可能一会就可用了。 |
15 | DATA_LOSS | Unrecoverable data loss or corruption. | 数据错误 |
16 | UNAUTHENTICATED | The request does not have valid authentication credentials for the operation. | 权限问题 |
20 | DO_NOT_USE_ RESERVED_FOR_ FUTURE_EXPANSION_ USE_DEFAULT_IN_ SWITCH_INSTEAD_ | An extra enum entry to prevent people from writing code that fails to compile when a new code is added. Nobody should ever reference this enumeration entry. In particular, if you write C++ code that switches on this enumeration, add a default: case instead of a case that mentions this enumeration entry. Nobody should rely on the value (currently 20) listed here. It may change in the future. |
06-27
08-27
1818
08-12
“相关推荐”对你有帮助么?
-
非常没帮助
-
没帮助
-
一般
-
有帮助
-
非常有帮助
提交