pkg: Index | Files

package errors

import ""


Package Files

error.go errorcode.go errorcode_string.go helpers.go

func DoNotWrap Uses

func DoNotWrap(err error) bool

DoNotWrap reports whether an error should not be wrapped in the Error type from this package. It returns true if err is a retry error, a context error, io.EOF, or if it wraps one of those.

func ErrorAs Uses

func ErrorAs(err error, target interface{}, errorAs func(error, interface{}) bool) bool

ErrorAs is a helper for the ErrorAs method of an API's portable type. It performs some initial nil checks, and does a single level of unwrapping when err is a *gcerr.Error. Then it calls its errorAs argument, which should be a driver implementation of ErrorAs.

type Error Uses

type Error struct {
    Code ErrorCode
    // contains filtered or unexported fields

An Error describes a Go CDK error.

func New Uses

func New(c ErrorCode, err error, callDepth int, msg string) *Error

New returns a new error with the given code, underlying error and message. Pass 1 for the call depth if New is called from the function raising the error; pass 2 if it is called from a helper function that was invoked by the original function; and so on.

func Newf Uses

func Newf(c ErrorCode, err error, format string, args ...interface{}) *Error

Newf uses format and args to format a message, then calls New.

func (*Error) Error Uses

func (e *Error) Error() string

func (*Error) Format Uses

func (e *Error) Format(s fmt.State, c rune)

Format error with xerrors

func (*Error) FormatError Uses

func (e *Error) FormatError(p xerrors.Printer) (next error)

FormatError ...

func (*Error) Unwrap Uses

func (e *Error) Unwrap() error

Unwrap returns the error underlying the receiver, which may be nil.

type ErrorCode Uses

type ErrorCode int

An ErrorCode describes the error's category.

const (
    // OK is returned on success.
    OK  ErrorCode = 0

    // Canceled indicates the operation was canceled (typically by the caller).
    Canceled ErrorCode = 1

    // Unknown error. An example of where this error may be returned is
    // if 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.
    Unknown ErrorCode = 2

    // InvalidArgument indicates client specified an invalid argument.
    // Note that this differs from FailedPrecondition. It indicates arguments
    // that are problematic regardless of the state of the system
    // (e.g., a malformed file name).
    InvalidArgument ErrorCode = 3

    // DeadlineExceeded means operation expired before completion.
    // 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 enough for the deadline to expire.
    DeadlineExceeded ErrorCode = 4

    // NotFound means some requested entity (e.g., file or directory) was
    // not found.
    NotFound ErrorCode = 5

    // AlreadyExists means an attempt to create an entity failed because one
    // already exists.
    AlreadyExists ErrorCode = 6

    // PermissionDenied indicates the caller does not have permission to
    // execute the specified operation. It must not be used for rejections
    // caused by exhausting some resource (use ResourceExhausted
    // instead for those errors). It must not be
    // used if the caller cannot be identified (use Unauthenticated
    // instead for those errors).
    PermissionDenied ErrorCode = 7

    // ResourceExhausted indicates some resource has been exhausted, perhaps
    // a per-user quota, or perhaps the entire file system is out of space.
    ResourceExhausted ErrorCode = 8

    // FailedPrecondition indicates operation was rejected because the
    // system is not in a state required for the operation's execution.
    // For example, directory to be deleted may be non-empty, an rmdir
    // operation is applied to a non-directory, etc.
    // A litmus test that may help a service implementor in deciding
    // 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., restarting 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
    //      they have first fixed up the directory by deleting files from it.
    //  (d) Use FailedPrecondition if the client performs conditional
    //      REST Get/Update/Delete on a resource and the resource on the
    //      server does not match the condition. E.g., conflicting
    //      read-modify-write on the same resource.
    FailedPrecondition ErrorCode = 9

    // Aborted indicates the operation was aborted, typically due to a
    // concurrency issue like sequencer check failures, transaction aborts,
    // etc.
    // See litmus test above for deciding between FailedPrecondition,
    // Aborted, and Unavailable.
    Aborted ErrorCode = 10

    // OutOfRange means 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.
    OutOfRange ErrorCode = 11

    // Unimplemented indicates operation is not implemented or not
    // supported/enabled in this service.
    Unimplemented ErrorCode = 12

    // Internal errors. Means some invariants expected by underlying
    // system has been broken. If you see one of these errors,
    // something is very broken.
    Internal ErrorCode = 13

    // Unavailable indicates the service is currently unavailable.
    // This is a most likely a transient condition and may be corrected
    // by retrying with a backoff. Note that it is not always safe to retry
    // non-idempotent operations.
    // See litmus test above for deciding between FailedPrecondition,
    // Aborted, and Unavailable.
    Unavailable ErrorCode = 14

    // DataLoss indicates unrecoverable data loss or corruption.
    DataLoss ErrorCode = 15

    // Unauthenticated indicates the request does not have valid
    // authentication credentials for the operation.
    Unauthenticated ErrorCode = 16

func GRPCCode Uses

func GRPCCode(err error) ErrorCode

GRPCCode extracts the gRPC status code and converts it into an ErrorCode. It returns Unknown if the error isn't from gRPC.

func (ErrorCode) String Uses

func (i ErrorCode) String() string

Package errors imports 8 packages (graph). Updated 2020-06-25. Refresh now. Tools for package owners.