Skip to content
Snippets Groups Projects
Verified Commit c4ae2fa3 authored by Timm Fitschen's avatar Timm Fitschen
Browse files

revert wrong styling

parent 624726cc
No related branches found
No related tags found
1 merge request!27F move entity
Pipeline #14861 failed
Stage: info
Stage: setup
Stage: test
Stage: deploy
Show whitespace changes
Inline Side-by-side
src/caosdb/status_code_description.cpp
+ 38
− 69
View file @ c4ae2fa3
......@@ -64,86 +64,56 @@ auto get_status_description(int code) -> const std::string & {
{StatusCode::CANCELLED, "The operation was canceled (typically by the caller)."},
{StatusCode::UNKNOWN, "Unknown error. This is typically a bug (server or client)."},
{StatusCode::INVALID_ARGUMENT,
"Client specified an invalid argument. Note that this differs from "
"FAILED_PRECONDITION. "
"INVALID_ARGUMENT indicates arguments that are problematic regardless of "
"the state of the "
"Client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. "
"INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the "
"system (e.g., a malformed file name)."},
{StatusCode::DEADLINE_EXCEEDED,
"Deadline expired before operation could complete. 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 expired before operation could complete. 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."},
{StatusCode::NOT_FOUND, "Some requested entity (e.g., file or directory) was not found."},
{StatusCode::ALREADY_EXISTS, "Some entity that we attempted to create "
"(e.g., file or directory) already exists."},
{StatusCode::ALREADY_EXISTS,
"Some entity that we attempted to create (e.g., file or directory) already exists."},
{StatusCode::PERMISSION_DENIED,
"The caller does not have permission to execute the specified operation. "
"PERMISSION_DENIED "
"must not be used for rejections caused by exhausting some resource (use "
"RESOURCE_EXHAUSTED "
"instead for those errors). PERMISSION_DENIED must not be used if the "
"caller can not be "
"The caller does not have permission to execute the specified operation. PERMISSION_DENIED "
"must not be used for rejections caused by exhausting some resource (use RESOURCE_EXHAUSTED "
"instead for those errors). PERMISSION_DENIED must not be used if the caller can not be "
"identified (use UNAUTHENTICATED instead for those errors)."},
{StatusCode::RESOURCE_EXHAUSTED, "Some resource has been exhausted, perhaps a per-user quota, "
"or perhaps the entire file system is out of space."},
{StatusCode::FAILED_PRECONDITION,
"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 FAILED_PRECONDITION, 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 "
"FAILED_PRECONDITION 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, FAILED_PRECONDITION "
"should be returned "
"since the client should not retry unless they have first fixed up the "
"directory by deleting "
"files from it. (d) Use FAILED_PRECONDITION if the client performs "
"conditional REST "
"Get/Update/Delete on a resource and the resource on the server does not "
"match the condition. "
"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 FAILED_PRECONDITION, 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 FAILED_PRECONDITION 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, FAILED_PRECONDITION should be returned "
"since the client should not retry unless they have first fixed up the directory by deleting "
"files from it. (d) Use FAILED_PRECONDITION 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."},
{StatusCode::ABORTED, "The operation was aborted, typically due to a "
"concurrency issue like sequencer check "
"failures, transaction aborts, etc. See litmus test "
"above for deciding between "
{StatusCode::ABORTED,
"The operation was aborted, typically due to a concurrency issue like sequencer check "
"failures, transaction aborts, etc. See litmus test above for deciding between "
"FAILED_PRECONDITION, ABORTED, and UNAVAILABLE."},
{StatusCode::OUT_OF_RANGE,
"Operation was attempted past the valid range. E.g., seeking or reading "
"past end of file. "
"Unlike INVALID_ARGUMENT, this error indicates a problem that may be "
"fixed if the system "
"state changes. For example, a 32-bit file system will generate "
"INVALID_ARGUMENT if asked to "
"read at an offset that is not in the range [0,2^32-1], but it will "
"generate OUT_OF_RANGE if "
"asked to read from an offset past the current file size. There is a fair "
"bit of overlap "
"between FAILED_PRECONDITION and OUT_OF_RANGE. We recommend using "
"OUT_OF_RANGE (the more "
"specific error) when it applies so that callers who are iterating "
"through a space can easily "
"Operation was attempted past the valid range. E.g., seeking or reading past end of file. "
"Unlike INVALID_ARGUMENT, this error indicates a problem that may be fixed if the system "
"state changes. For example, a 32-bit file system will generate INVALID_ARGUMENT if asked to "
"read at an offset that is not in the range [0,2^32-1], but it will generate OUT_OF_RANGE if "
"asked to read from an offset past the current file size. There is a fair bit of overlap "
"between FAILED_PRECONDITION and OUT_OF_RANGE. We recommend using OUT_OF_RANGE (the more "
"specific error) when it applies so that callers who are iterating through a space can easily "
"look for an OUT_OF_RANGE error to detect when they are done."},
{StatusCode::UNIMPLEMENTED,
"Operation is not implemented or not supported/enabled in this service. "
"In contrast to "
"UNSUPPORTED_FEATURE (which is a client error) this error indicates that "
"the server does not "
"Operation is not implemented or not supported/enabled in this service. In contrast to "
"UNSUPPORTED_FEATURE (which is a client error) this error indicates that the server does not "
"support this operation."},
{StatusCode::INTERNAL,
"Internal errors. Means some invariants expected by underlying System has "
"been broken. If you "
"Internal errors. Means some invariants expected by underlying System has been broken. If you "
"see one of these errors, Something is very broken. "},
{StatusCode::DATA_LOSS, "Unrecoverable data loss or corruption."},
......@@ -186,10 +156,9 @@ auto get_status_description(int code) -> const std::string & {
"to delete the old pointee first."},
{StatusCode::ENUM_MAPPING_ERROR,
"The role, importance, or datatype you specified does not exist."},
{StatusCode::SPOILED, "The object has been used in a way that left it in a "
"corrupted state. This does not indicate "
"any form of misuse. It just indicates that the "
"object is spoiled for further use now."},
{StatusCode::SPOILED,
"The object has been used in a way that left it in a corrupted state. This does not indicate "
"any form of misuse. It just indicates that the object is spoiled for further use now."},
{StatusCode::OTHER_CLIENT_ERROR,
"This is code is reserved to errors raised by other clients wrapping the "
"C++ client (or its Extern C interface). This should never occur when "
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment