Home
last modified time | relevance | path

Searched refs:details (Results 1 – 13 of 13) sorted by relevance

/tonic/tonic-types/src/richer_error/
H A Dmod.rs41 details, in gen_details_bytes()
75 details: ErrorDetails, in with_error_details_and_metadata()
97 details: ErrorDetails, in with_error_details()
487 details: ErrorDetails, in with_error_details_and_metadata()
601 details, in with_error_details_vec()
763 for any in self.details.iter() { in check_error_details()
799 Ok(details) in check_error_details()
807 let mut details: Vec<ErrorDetail> = Vec::with_capacity(self.details.len()); in check_error_details_vec() localVariable
809 for any in self.details.iter() { in check_error_details_vec()
845 Ok(details) in check_error_details_vec()
[all …]
/tonic/tonic-types/proto/
H A Dstatus.proto31 // three pieces of data: error code, error message, and error details.
41 // [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
44 // A list of messages that carry the error details. There is a common set of
46 repeated google.protobuf.Any details = 3; field
H A Derror_details.proto63 // Also see RetryInfo and Help types for other details about handling a
88 // Describes the cause of the error with structured details.
128 // Additional structured details about this error.
/tonic/tonic-types/
H A DREADME.md15 be used on the server side to create a status with error details, which can then
17 [`tonic::Status`] that can be used by a tonic client to extract error details,
38 // Add error details conditionally
53 // Check if any error details were set and return error status if so
55 // Add additional error details if necessary
88 // Handle bad_request details
91 // Handle help details
94 // Handle localized_message details
110 [`tonic::Status`] is presented, using vectors of error details structs wrapped
117 Besides that, multiple examples with alternative error details extraction
/tonic/tonic/src/
H A Dstatus.rs44 details: Bytes, field
166 details: Bytes::new(), in new()
479 details, in from_header_map()
496 pub fn details(&self) -> &[u8] { in details() method
497 &self.details in details()
534 let details = crate::util::base64::STANDARD_NO_PAD.encode(&self.details[..]); in add_header() localVariable
559 details: Bytes, in with_details_and_metadata()
565 details, in with_details_and_metadata()
603 details: status.details.clone(), in find_status_in_source_chain()
719 self.details(), in fmt()
[all …]
/tonic/.github/ISSUE_TEMPLATE/
H A Dbug_report.md45 Enter your issue details below this comment.
/tonic/tonic-types/src/generated/
H A Dgoogle_rpc.rs22 pub details: ::prost::alloc::vec::Vec<::prost_types::Any>, field
/tonic/tests/integration_tests/tests/
H A Dstatus.rs61 assert_eq!(err.details(), &[1]); in status_with_details()
/tonic/examples/
H A Dhelloworld-tutorial.md136 …ays, we will not get into the details in this introductory tutorial. Please see the [tonic-build] …
/tonic/
H A DCONTRIBUTING.md43 supporting details (a test case that demonstrates a bug), providing
285 the details, but feel free to skip parts if you're not sure what to put.
302 more details.
H A DCHANGELOG.md128 * **tonic-types:** add ability to extract rich error details from `google.rpc.Status` ([#1430](http…
500 * `Status::details` leaking base64 encoding ([#395](https://github.com/hyperium/tonic/issues/395)) …
526 * base64 encode details header ([#345](https://github.com/hyperium/tonic/issues/345)) ([e683ffe](ht…
/tonic/examples/proto/googleapis/google/api/
H A Dhttp.proto316 // Refer to [selector][google.api.DocumentationRule.selector] for syntax details.
/tonic/examples/proto/googleapis/google/pubsub/v1/
H A Dpubsub.proto431 // Gets the configuration details of a subscription.
537 // Gets the configuration details of a snapshot. Snapshots are used in