Код ошибки 701 grpc

Status codes and their use in gRPC

gRPC uses a set of well defined status codes as part of the RPC API. These
statuses are defined as such:

Code	Number	Description
OK	0	Not an error; returned on success.
CANCELLED	1	The operation was cancelled, typically by the caller.
UNKNOWN	2	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.
INVALID_ARGUMENT	3	The 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).
DEADLINE_EXCEEDED	4	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
NOT_FOUND	5	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, NOT_FOUND may be used. If a request is denied for some users within a class of users, such as user-based access control, PERMISSION_DENIED must be used.
ALREADY_EXISTS	6	The entity that a client attempted to create (e.g., file or directory) already exists.
PERMISSION_DENIED	7	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). This error code does not imply the request is valid or the requested entity exists or satisfies other pre-conditions.
RESOURCE_EXHAUSTED	8	Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
FAILED_PRECONDITION	9	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 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., when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence). (c) 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 the files are deleted from the directory.
ABORTED	10	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 FAILED_PRECONDITION, ABORTED, and UNAVAILABLE.
OUT_OF_RANGE	11	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.
UNIMPLEMENTED	12	The operation is not implemented or is not supported/enabled in this service.
INTERNAL	13	Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors.
UNAVAILABLE	14	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.
DATA_LOSS	15	Unrecoverable data loss or corruption.
UNAUTHENTICATED	16	The request does not have valid authentication credentials for the operation.

All RPCs started at a client return a status object composed of an integer
code and a string message. The server-side can choose the status it
returns for a given RPC.

The gRPC client and server-side implementations may also generate and
return status on their own when errors happen. Only a subset of
the pre-defined status codes are generated by the gRPC libraries. This
allows applications to be sure that any other code it sees was actually
returned by the application (although it is also possible for the
server-side to return one of the codes generated by the gRPC libraries).

The following table lists the codes that may be returned by the gRPC
libraries (on either the client-side or server-side) and summarizes the
situations in which they are generated.

Case	Code	Generated at Client or Server
Client Application cancelled the request	CANCELLED	Both
Deadline expires before server returns status	DEADLINE_EXCEEDED	Both
Method not found at server	UNIMPLEMENTED	Server
Server shutting down	UNAVAILABLE	Server
Server side application throws an exception (or does something other than returning a Status code to terminate an RPC)	UNKNOWN	Server
No response received before Deadline expires. This may occur either when the client is unable to send the request to the server or when the server fails to respond in time.	DEADLINE_EXCEEDED	Both
Some data transmitted (e.g., request metadata written to TCP connection) before connection breaks	UNAVAILABLE	Client
Could not decompress, but compression algorithm supported (Client -> Server)	INTERNAL	Server
Could not decompress, but compression algorithm supported (Server -> Client)	INTERNAL	Client
Compression mechanism used by client not supported at server	UNIMPLEMENTED	Server
Server temporarily out of resources (e.g., Flow-control resource limits reached)	RESOURCE_EXHAUSTED	Server
Client does not have enough memory to hold the server response	RESOURCE_EXHAUSTED	Client
Flow-control protocol violation	INTERNAL	Both
Error parsing returned status	UNKNOWN	Client
Incorrect Auth metadata ( Credentials failed to get metadata, Incompatible credentials set on channel and call, Invalid host set in :authority metadata, etc.)	UNAUTHENTICATED	Both
Request cardinality violation (method requires exactly one request but client sent some other number of requests)	UNIMPLEMENTED	Server
Response cardinality violation (method requires exactly one response but server sent some other number of responses)	UNIMPLEMENTED	Client
Error parsing response proto	INTERNAL	Client
Error parsing request proto	INTERNAL	Server
Sent or received message was larger than configured limit	RESOURCE_EXHAUSTED	Both
Keepalive watchdog times out	UNAVAILABLE	Both

The following status codes are never generated by the library:

• INVALID_ARGUMENT
• NOT_FOUND
• ALREADY_EXISTS
• FAILED_PRECONDITION
• ABORTED
• OUT_OF_RANGE
• DATA_LOSS

Applications that may wish to retry failed RPCs must decide which status codes on which to retry. As shown in the table above, the gRPC library can generate the same status code for different cases. Server applications can also return those same status codes. Therefore, there is no fixed list of status codes on which it is appropriate to retry in all applications. As a result, individual applications must make their own determination as to which status codes should cause an RPC to be retried.

How gRPC deals with errors, and gRPC error codes.

gRPC uses a set of well defined status codes as part of the RPC API. These statuses are defined as such:

Code	Number	Description
OK	0	Not an error; returned on success.
CANCELLED	1	The operation was cancelled, typically by the caller.
UNKNOWN	2	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.
INVALID_ARGUMENT	3	The 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).
DEADLINE_EXCEEDED	4	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
NOT_FOUND	5	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, NOT_FOUND may be used. If a request is denied for some users within a class of users, such as user-based access control, PERMISSION_DENIED must be used.
ALREADY_EXISTS	6	The entity that a client attempted to create (e.g., file or directory) already exists.
PERMISSION_DENIED	7	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). This error code does not imply the request is valid or the requested entity exists or satisfies other pre-conditions.
RESOURCE_EXHAUSTED	8	Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
FAILED_PRECONDITION	9	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 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., when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence). (c) 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 the files are deleted from the directory.
ABORTED	10	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 FAILED_PRECONDITION, ABORTED, and UNAVAILABLE.
OUT_OF_RANGE	11	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.
UNIMPLEMENTED	12	The operation is not implemented or is not supported/enabled in this service.
INTERNAL	13	Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors.
UNAVAILABLE	14	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.
DATA_LOSS	15	Unrecoverable data loss or corruption.
UNAUTHENTICATED	16	The request does not have valid authentication credentials for the operation.

All RPCs started at a client return a status object composed of an integer code and a string message. The server-side can choose the status it returns for a given RPC.

The gRPC client and server-side implementations may also generate and return status on their own when errors happen. Only a subset of the pre-defined status codes are generated by the gRPC libraries. This allows applications to be sure that any other code it sees was actually returned by the application (although it is also possible for the server-side to return one of the codes generated by the gRPC libraries).

The following table lists the codes that may be returned by the gRPC libraries (on either the client-side or server-side) and summarizes the situations in which they are generated.

Case	Code	Generated at Client or Server
Client Application cancelled the request	CANCELLED	Both
Deadline expires before server returns status	DEADLINE_EXCEEDED	Both
Method not found at server	UNIMPLEMENTED	Server
Server shutting down	UNAVAILABLE	Server
Server side application throws an exception (or does something other than returning a Status code to terminate an RPC)	UNKNOWN	Server
No response received before Deadline expires. This may occur either when the client is unable to send the request to the server or when the server fails to respond in time.	DEADLINE_EXCEEDED	Both
Some data transmitted (e.g., request metadata written to TCP connection) before connection breaks	UNAVAILABLE	Client
Could not decompress, but compression algorithm supported (Client -> Server)	INTERNAL	Server
Could not decompress, but compression algorithm supported (Server -> Client)	INTERNAL	Client
Compression mechanism used by client not supported at server	UNIMPLEMENTED	Server
Server temporarily out of resources (e.g., Flow-control resource limits reached)	RESOURCE_EXHAUSTED	Server
Client does not have enough memory to hold the server response	RESOURCE_EXHAUSTED	Client
Flow-control protocol violation	INTERNAL	Both
Error parsing returned status	UNKNOWN	Client
Incorrect Auth metadata ( Credentials failed to get metadata, Incompatible credentials set on channel and call, Invalid host set in :authority metadata, etc.)	UNAUTHENTICATED	Both
Request cardinality violation (method requires exactly one request but client sent some other number of requests)	UNIMPLEMENTED	Server
Response cardinality violation (method requires exactly one response but server sent some other number of responses)	UNIMPLEMENTED	Client
Error parsing response proto	INTERNAL	Client
Error parsing request proto	INTERNAL	Server
Sent or received message was larger than configured limit	RESOURCE_EXHAUSTED	Both
Keepalive watchdog times out	UNAVAILABLE	Both

The following status codes are never generated by the library:

• INVALID_ARGUMENT
• NOT_FOUND
• ALREADY_EXISTS
• FAILED_PRECONDITION
• ABORTED
• OUT_OF_RANGE
• DATA_LOSS

Applications that may wish to retry failed RPCs must decide which status codes on which to retry. As shown in the table above, the gRPC library can generate the same status code for different cases. Server applications can also return those same status codes. Therefore, there is no fixed list of status codes on which it is appropriate to retry in all applications. As a result, individual applications must make their own determination as to which status codes should cause an RPC to be retried.

This chapter provides an overview of the error model for Google APIs. It also
provides general guidance to developers on how to properly generate and
handle errors.

Google APIs use a simple protocol-agnostic error model, which allows us to
offer a consistent experience across different APIs, different API protocols
(such as gRPC or HTTP), and different error contexts (such as asynchronous,
batch, or workflow errors).

Error Model

The error model for Google APIs is logically defined by
google.rpc.Status,
an instance of which is returned to the client when an API error occurs. The
following code snippet shows the overall design of the error model:

package google.rpc;

// The `Status` type defines a logical error model that is suitable for
// different programming environments, including REST APIs and RPC APIs.
message Status {
  // A simple error code that can be easily handled by the client. The
  // actual error code is defined by `google.rpc.Code`.
  int32 code = 1;

  // A developer-facing human-readable error message in English. It should
  // both explain the error and offer an actionable resolution to it.
  string message = 2;

  // Additional error information that the client code can use to handle
  // the error, such as retry info or a help link.
  repeated google.protobuf.Any details = 3;
}

Because most Google APIs use resource-oriented API design, the error handling
follows the same design principle by using a small set of standard errors with a
large number of resources. For example, instead of defining different kinds of
«not found» errors, the server uses one standard google.rpc.Code.NOT_FOUND
error code and tells the client which specific resource was not found. The
smaller error space reduces the complexity of documentation, affords better
idiomatic mappings in client libraries, and reduces client logic complexity
while not restricting the inclusion of actionable information.

Error Codes

Google APIs must use the canonical error codes defined by
google.rpc.Code.
Individual APIs must avoid defining additional error codes, since
developers are very unlikely to write logic to handle a large number of error
codes. For reference, handling an average of three error codes per API call
would mean most application logic would just be for error handling, which would
not be a good developer experience.

Error Messages

The error message should help users understand and resolve the API error
easily and quickly. In general, consider the following guidelines when writing
error messages:

• Do not assume the user is an expert user of your API. Users could be client
  developers, operations people, IT staff, or end-users of apps.
• Do not assume the user knows anything about your service implementation or
  is familiar with the context of the errors (such as log analysis).
• When possible, error messages should be constructed such that a technical
  user (but not necessarily a developer of your API) can respond to the error
  and correct it.
• Keep the error message brief. If needed, provide a link where a confused
  reader can ask questions, give feedback, or get more information that
  doesn’t cleanly fit in an error message. Otherwise, use the details field to
  expand.

Error Details

Google APIs define a set of standard error payloads for error details, which you
can find in
google/rpc/error_details.proto.
These cover the most common needs for API errors, such as quota failure and
invalid parameters. Like error codes, developers should use these standard
payloads whenever possible.

Additional error detail types should only be introduced if they can assist
application code to handle the errors. If the error information can only be
handled by humans, rely on the error message content and let developers handle
it manually rather than introducing additional error detail types.

Here are some example error_details payloads:

• ErrorInfo: Provides structured error information that is both stable
  and extensible.
• RetryInfo: Describes when clients can retry a failed request, may be
  returned on Code.UNAVAILABLE or Code.ABORTED
• QuotaFailure: Describes how a quota check failed, may be returned on
  Code.RESOURCE_EXHAUSTED
• BadRequest: Describes violations in a client request, may be returned on
  Code.INVALID_ARGUMENT

Error Info

ErrorInfo is a special kind of error payload. It provides stable and
extensible error information that both humans and applications can depend on.
Each ErrorInfo has three pieces of information: an error domain, an error
reason, and a set of error metadata, such as this
example.
For more information, see the
ErrorInfo
definition.

For Google APIs, the primary error domain is googleapis.com, and the
corresponding error reasons are defined by google.api.ErrorReason enum.
For more information, see the
google.api.ErrorReason
definition.

Error Localization

The message field in
google.rpc.Status
is developer-facing and must be in English.

If a user-facing error message is needed, use
google.rpc.LocalizedMessage
as your details field. While the message field in
google.rpc.LocalizedMessage
can be localized, ensure that the message field in
google.rpc.Status
is in English.

By default, the API service should use the authenticated user’s locale or HTTP
Accept-Language header or the language_code parameter in the request to
determine the language for the localization.

Error Mapping

Google APIs are accessible in different programming environments. Each
environment typically has its own way of error handling. The following
sections explain how the error model is mapped in commonly used environments.

HTTP Mapping

While proto3 messages have native JSON encoding, Google’s API Platform uses a
different error schema for Google’s JSON HTTP APIs for backward compatibility
reasons.

Schema:

// This message defines the error schema for Google's JSON HTTP APIs.
message Error {
  // Deprecated. This message is only used by error format v1.
  message ErrorProto {}
  // This message has the same semantics as `google.rpc.Status`. It uses HTTP
  // status code instead of gRPC status code. It has extra fields `status` and
  // `errors` for backward compatibility with [Google API Client
  // Libraries](https://developers.google.com/api-client-library).
  message Status {
    // The HTTP status code that corresponds to `google.rpc.Status.code`.
    int32 code = 1;
    // This corresponds to `google.rpc.Status.message`.
    string message = 2;
    // Deprecated. This field is only used by error format v1.
    repeated ErrorProto errors = 3;
    // This is the enum version for `google.rpc.Status.code`.
    google.rpc.Code status = 4;
    // This corresponds to `google.rpc.Status.details`.
    repeated google.protobuf.Any details = 5;
  }
  // The actual error payload. The nested message structure is for backward
  // compatibility with [Google API Client
  // Libraries](https://developers.google.com/api-client-library). It also
  // makes the error more readable to developers.
  Status error = 1;
}

Example (link):

{
  "error": {
    "code": 400,
    "message": "API key not valid. Please pass a valid API key.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
        "reason": "API_KEY_INVALID",
        "domain": "googleapis.com",
        "metadata": {
          "service": "translate.googleapis.com"
        }
      }
    ]
  }
}

gRPC Mapping

Different RPC protocols map the error model differently. For
gRPC, the error model is natively supported by the generated
code and the runtime library in each supported language. You can find out more
in gRPC’s API documentation. For example, see gRPC Java’s
io.grpc.Status.

Client Library Mapping

Google client libraries may choose to surface errors differently per language to
be consistent with established idioms. For example, the
google-cloud-go
library will return an error that implements the same interface as
google.rpc.Status,
while
google-cloud-java
will raise an Exception.

Handling Errors

Below is a table containing all of the gRPC error codes defined in
google.rpc.Code
and a short description of their cause. To handle an error, you can check the
description for the returned status code and modify your call accordingly.

HTTP	gRPC	Description
200	OK	No error.
400	INVALID_ARGUMENT	Client specified an invalid argument. Check error message and error details for more information.
400	FAILED_PRECONDITION	Request can not be executed in the current system state, such as deleting a non-empty directory.
400	OUT_OF_RANGE	Client specified an invalid range.
401	UNAUTHENTICATED	Request not authenticated due to missing, invalid, or expired OAuth token.
403	PERMISSION_DENIED	Client does not have sufficient permission. This can happen because the OAuth token does not have the right scopes, the client doesn’t have permission, or the API has not been enabled.
404	NOT_FOUND	A specified resource is not found.
409	ABORTED	Concurrency conflict, such as read-modify-write conflict.
409	ALREADY_EXISTS	The resource that a client tried to create already exists.
429	RESOURCE_EXHAUSTED	Either out of resource quota or reaching rate limiting. The client should look for google.rpc.QuotaFailure error detail for more information.
499	CANCELLED	Request cancelled by the client.
500	DATA_LOSS	Unrecoverable data loss or data corruption. The client should report the error to the user.
500	UNKNOWN	Unknown server error. Typically a server bug.
500	INTERNAL	Internal server error. Typically a server bug.
501	NOT_IMPLEMENTED	API method not implemented by the server.
502	N/A	Network error occurred before reaching the server. Typically a network outage or misconfiguration.
503	UNAVAILABLE	Service unavailable. Typically the server is down.
504	DEADLINE_EXCEEDED	Request deadline exceeded. This will happen only if the caller sets a deadline that is shorter than the method’s default deadline (i.e. requested deadline is not enough for the server to process the request) and the request did not finish within the deadline.

Retrying Errors

Clients may retry on 503 UNAVAILABLE errors with exponential backoff.
The minimum delay should be 1s unless it is documented otherwise. The default
retry repetition should be once unless it is documented otherwise.

For 429 RESOURCE_EXHAUSTED errors, the client may retry at the higher level
with minimum 30s delay. Such retries are only useful for long running
background jobs.

For all other errors, retry may not be applicable. First ensure your request
is idempotent, and see
google.rpc.RetryInfo
for guidance.

Propagating Errors

If your API service depends on other services, you should not blindly propagate
errors from those services to your clients. When translating errors, we suggest
the following:

• Hide implementation details and confidential information.
• Adjust the party responsible for the error. For example, a server that
  receives an INVALID_ARGUMENT error from another service should propagate
  an INTERNAL to its own caller.

Reproducing Errors

If you cannot resolve errors through analysis of logs and monitoring, you should
try to reproduce the errors with a simple and repeatable test. You can use the
test to collect more information for troubleshooting, which you can provide
when contacting technical support.

We recommend you use curl -v and
System Parameters to reproduce errors with
Google APIs. Together they can reproduce almost all Google API requests,
and provide you verbose debug information. For more information, see the
respective documentation pages for the API you are calling.

Generating Errors

If you are a server developer, you should generate errors with enough
information to help client developers understand and resolve the problem. At the
same time, you must be aware of the security and privacy of the user data, and
avoid disclosing sensitive information in the error message and error details,
since errors are often logged and may be accessible by others. For example, an
error message like «Client IP address is not on allowlist 128.0.0.0/8» exposes
information about the server-side policy, which may not be accessible to the
user who has access to the logs.

To generate proper errors, you first need to be familiar with google.rpc.Code to
choose the most suitable error code for each error condition. A server
application may check multiple error conditions in parallel, and return the
first one.

The following table lists each error code and an example of a good error
message.

HTTP	gRPC	Example Error Message
400	INVALID_ARGUMENT	Request field x.y.z is xxx, expected one of [yyy, zzz].
400	FAILED_PRECONDITION	Resource xxx is a non-empty directory, so it cannot be deleted.
400	OUT_OF_RANGE	Parameter ‘age’ is out of range [0, 125].
401	UNAUTHENTICATED	Invalid authentication credentials.
403	PERMISSION_DENIED	Permission ‘xxx’ denied on resource ‘yyy’.
404	NOT_FOUND	Resource ‘xxx’ not found.
409	ABORTED	Couldn’t acquire lock on resource ‘xxx’.
409	ALREADY_EXISTS	Resource ‘xxx’ already exists.
429	RESOURCE_EXHAUSTED	Quota limit ‘xxx’ exceeded.
499	CANCELLED	Request cancelled by the client.
500	DATA_LOSS	See note.
500	UNKNOWN	See note.
500	INTERNAL	See note.
501	NOT_IMPLEMENTED	Method ‘xxx’ not implemented.
503	UNAVAILABLE	See note.
504	DEADLINE_EXCEEDED	See note.

Error Payloads

The google.rpc package defines a set of standard error payloads, which are
preferred to custom error payloads. The following table lists each error code
and its matching standard error payload, if applicable. We recommend advanced
applications look for these error payloads in google.rpc.Status when they
handle errors.

HTTP	gRPC	Recommended Error Detail
400	INVALID_ARGUMENT	google.rpc.BadRequest
400	FAILED_PRECONDITION	google.rpc.PreconditionFailure
400	OUT_OF_RANGE	google.rpc.BadRequest
401	UNAUTHENTICATED	google.rpc.ErrorInfo
403	PERMISSION_DENIED	google.rpc.ErrorInfo
404	NOT_FOUND	google.rpc.ResourceInfo
409	ABORTED	google.rpc.ErrorInfo
409	ALREADY_EXISTS	google.rpc.ResourceInfo
429	RESOURCE_EXHAUSTED	google.rpc.QuotaFailure
499	CANCELLED
500	DATA_LOSS	google.rpc.DebugInfo
500	UNKNOWN	google.rpc.DebugInfo
500	INTERNAL	google.rpc.DebugInfo
501	NOT_IMPLEMENTED
503	UNAVAILABLE	google.rpc.DebugInfo
504	DEADLINE_EXCEEDED	google.rpc.DebugInfo