pub enum Code {
Show 18 variants
Ok,
Cancelled,
Unknown,
InvalidArgument,
DeadlineExceeded,
NotFound,
AlreadyExists,
PermissionDenied,
ResourceExhausted,
FailedPrecondition,
Aborted,
OutOfRange,
Unimplemented,
Internal,
Unavailable,
DataLoss,
Unauthenticated,
Other(u16),
}Expand description
GRPC status code
Reference: https://github.com/grpc/grpc/blob/master/doc/statuscodes.md#status-codes-and-their-use-in-grpc
Variants§
Ok
Not an error.
Cancelled
The operation was cancelled, typically by the caller.
Unknown
Unknown error.
For example, this error may be returned when 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.
InvalidArgument
The client specified an invalid argument.
Note that this differs from FailedPrecondition. InvalidArgument
indicates arguments that are problematic regardless of the state of the
system (e.g., a malformed file name).
DeadlineExceeded
The deadline expired before the 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.
NotFound
Some requested entity
(e.g., file or directory) was not found. Note to server developers: if a
request is denied for an entire class of users, such as gradual feature
rollout or undocumented allowlist, NotFound may be used. If a request
is denied for some users within a class of users, such as user-based
access control, PermissionDenied must be used.
AlreadyExists
The entity that a client attempted to create (e.g., file or directory) already exists.
PermissionDenied
The caller does not have permission to execute the specified operation.
PermissionDenied must not be used for rejections caused by exhausting
some resource (use ResourceExhausted instead for those errors).
PermissionDenied must not be used if the caller can not be identified
(use Unauthenticated instead for those errors). This error code does
not imply the request is valid or the requested entity exists or
satisfies other pre-conditions.
ResourceExhausted
Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
FailedPrecondition
The operation was rejected because the system is not in a state required for the operation’s execution.
For example, the directory to be deleted is non-empty, an rmdir
operation is applied to a non-directory, etc. Service implementors can
use the following guidelines to decide between FailedPrecondition,
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., when a client-specified test-and-set fails, indicating
the client should restart a read-modify-write sequence).
(c) Use FailedPrecondition 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,
FailedPrecondition should be returned since the client
should not retry unless the files are deleted from the
directory.
Aborted
The operation was aborted, typically due to a concurrency issue such as
a sequencer check failure or transaction abort. See the guidelines above
for deciding between FailedPrecondition, Aborted, and Unavailable.
OutOfRange
The operation was attempted past the valid range. E.g., seeking or reading past end-of-file.
Unlike InvalidArgument, this error indicates
a problem that may be fixed if the system state changes. For example, a
32-bit file system will generate InvalidArgument if asked to read at
an offset that is not in the range [0,2^32-1], but it will generate
OutOfRange if asked to read from an offset past the current file size.
There is a fair bit of overlap between FailedPrecondition and
OutOfRange. We recommend using OutOfRange (the more specific error)
when it applies so that callers who are iterating through a space can
easily look for an OutOfRange error to detect when they are done.
Unimplemented
The operation is not implemented or is not supported/enabled in this service.
Internal
Internal errors.
This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors.
The service is currently unavailable.
This is most likely a transient condition, which can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations.
DataLoss
Unrecoverable data loss or corruption.
Unauthenticated
The request does not have valid authentication credentials for the operation.
Other(u16)
Other codes
Implementations§
Trait Implementations§
impl Copy for Code
impl Eq for Code
impl StructuralPartialEq for Code
Auto Trait Implementations§
impl Freeze for Code
impl RefUnwindSafe for Code
impl Send for Code
impl Sync for Code
impl Unpin for Code
impl UnwindSafe for Code
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<Q, K> Equivalent<K> for Q
impl<Q, K> Equivalent<K> for Q
Source§impl<Q, K> Equivalent<K> for Q
impl<Q, K> Equivalent<K> for Q
Source§fn equivalent(&self, key: &K) -> bool
fn equivalent(&self, key: &K) -> bool
key and return true if they are equal.