grpc v0.3.1 GRPC.Status View Source
Collection of gRPC status.
Please refer to https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/status.h
Link to this section Summary
Functions
The operation was aborted
Some entity that we attempted to create (e.g., file or directory) already exists
The operation was cancelled (typically by the caller)
Unrecoverable data loss or corruption
Deadline expired before operation could complete
Operation was rejected because the system is not in a state required for the operation’s execution
Internal errors
Client specified an invalid argument
Some requested entity (e.g., file or directory) was not found
Not an error; returned on success
Operation was attempted past the valid range
The caller does not have permission to execute the specified operation
Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space
The request does not have valid authentication credentials for the operation
The service is currently unavailable
Operation is not implemented or not supported/enabled in this service
Unknown error
Link to this section Types
Link to this section Functions
The operation was aborted.
Typically due to a concurrency issue like sequencer check failures, transaction aborts, etc.
Some entity that we attempted to create (e.g., file or directory) already exists.
The operation was cancelled (typically by the caller).
Unrecoverable data loss or corruption.
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.
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.
Internal errors.
Means some invariants expected by underlying system has been broken. If you see one of these errors, something is very broken.
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).
Some requested entity (e.g., file or directory) was not found.
Not an error; returned on success.
Operation was attempted past the valid range.
E.g., seeking or reading past end of file.
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).
Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
The request does not have valid authentication credentials for the operation.
Operation is not implemented or not supported/enabled in this service.
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.