Modules§

Structs§

  • Describes violations in a client request. This error type focuses on the syntactic aspects of the request.
  • Describes additional debugging info.
  • Describes the cause of the error with structured details.
  • Provides links to documentation or for performing an out of band action.
  • Represents an HTTP header.
  • Represents an HTTP request.
  • Represents an HTTP response.
  • Provides a localized error message that is safe to return to the user which can be attached to an RPC error.
  • Describes what preconditions have failed.
  • Describes how a quota check failed.
  • Contains metadata about the request that clients can attach when filing a bug or providing other forms of feedback.
  • Describes the resource that is being accessed.
  • Describes when the clients can retry a failed request. Clients could ignore the recommendation here or retry when this information is missing from error responses.
  • 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. Each Status message contains three pieces of data: error code, error message, and error details.

Enums§

  • The canonical error codes for gRPC APIs.