d1563f0ccd
* Update tonic & prost, and regenerate proto * Reignore doc code * Revert pull #14367, but pin tokio to v0.2 for jsonrpc * Bump backoff and goauth -> and therefore tokio * Bump tokio in faucet, net-utils * Bump remaining tokio, plus tarpc
23 lines
1.2 KiB
Rust
23 lines
1.2 KiB
Rust
/// The `Status` type defines a logical error model that is suitable for
|
|
/// different programming environments, including REST APIs and RPC APIs. It is
|
|
/// used by [gRPC](https://github.com/grpc). Each `Status` message contains
|
|
/// three pieces of data: error code, error message, and error details.
|
|
///
|
|
/// You can find out more about this error model and how to work with it in the
|
|
/// [API Design Guide](https://cloud.google.com/apis/design/errors).
|
|
#[derive(Clone, PartialEq, ::prost::Message)]
|
|
pub struct Status {
|
|
/// The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
|
|
#[prost(int32, tag = "1")]
|
|
pub code: i32,
|
|
/// A developer-facing error message, which should be in English. Any
|
|
/// user-facing error message should be localized and sent in the
|
|
/// [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
|
|
#[prost(string, tag = "2")]
|
|
pub message: ::prost::alloc::string::String,
|
|
/// A list of messages that carry the error details. There is a common set of
|
|
/// message types for APIs to use.
|
|
#[prost(message, repeated, tag = "3")]
|
|
pub details: ::prost::alloc::vec::Vec<::prost_types::Any>,
|
|
}
|