README
¶
errors wrappers
This package provides convenience wrappers for errors.
Each function in the package behaves like fmt.Errorf function, attaching corresponding HTTP status. The mapping of HTTP statuses:
| Function | HTTP code |
|---|---|
| Aborted | 409 Conflict |
| AlreadyExists | 409 Conflict |
| Canceled | 499 Client Closed Request |
| DataLoss | 500 Internal Server Error |
| DeadlineExceeded | 504 Gateway Timeout |
| FailedPrecondition | 400 Bad Request |
| Internal | 500 Internal Server Error |
| InvalidArgument | 400 Bad Request |
| NotFound | 404 Not Found |
| OutOfRange | 400 Bad Request |
| PermissionDenied | 403 Forbidden |
| ResourceExhausted | 429 Too Many Requests |
| Unauthenticated | 401 Unauthorized |
| Unavailable | 503 Service Unavailable |
| Unimplemented | 501 Not Implemented |
| Unknown | 500 Internal Server Error |
The list can be found here.
Documentation
¶
Index ¶
- type CodeError
- func Aborted(format string, a ...interface{}) *CodeError
- func AlreadyExists(format string, a ...interface{}) *CodeError
- func Canceled(format string, a ...interface{}) *CodeError
- func DataLoss(format string, a ...interface{}) *CodeError
- func DeadlineExceeded(format string, a ...interface{}) *CodeError
- func FailedPrecondition(format string, a ...interface{}) *CodeError
- func Internal(format string, a ...interface{}) *CodeError
- func InvalidArgument(format string, a ...interface{}) *CodeError
- func NotFound(format string, a ...interface{}) *CodeError
- func OutOfRange(format string, a ...interface{}) *CodeError
- func PermissionDenied(format string, a ...interface{}) *CodeError
- func ResourceExhausted(format string, a ...interface{}) *CodeError
- func Unauthenticated(format string, a ...interface{}) *CodeError
- func Unavailable(format string, a ...interface{}) *CodeError
- func Unimplemented(format string, a ...interface{}) *CodeError
- func Unknown(format string, a ...interface{}) *CodeError
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type CodeError ¶
type CodeError struct {
// contains filtered or unexported fields
}
func Aborted ¶
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.
func AlreadyExists ¶
AlreadyExists means an attempt to create an entity failed because one already exists.
func DeadlineExceeded ¶
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.
func FailedPrecondition ¶
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.
func Internal ¶
Internal errors. Means some invariants expected by underlying system has been broken. If you see one of these errors, something is very broken.
func InvalidArgument ¶
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).
func OutOfRange ¶
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.
func PermissionDenied ¶
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).
func ResourceExhausted ¶
ResourceExhausted indicates some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
func Unauthenticated ¶
Unauthenticated indicates the request does not have valid authentication credentials for the operation.
func Unavailable ¶
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.
func Unimplemented ¶
Unimplemented indicates operation is not implemented or not supported/enabled in this service.
func Unknown ¶
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.
Source Files