-
- All Implemented Interfaces:
-
co.electriccoin.lightwallet.client.model.Response,co.electriccoin.lightwallet.client.model.Response.Failure
public class Response.Failure.Server<T extends Object> implements Response.Failure<T>
The server did respond and returned an error.
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description public final classResponse.Failure.Server.AbortedThe operation was aborted, typically due to a concurrency issue like sequencer check failures, transaction aborts, etc.
public final classResponse.Failure.Server.DeadlineExceededDeadline 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.
public final classResponse.Failure.Server.NotFoundSome requested entity (e.g., file or directory) was not found.
public final classResponse.Failure.Server.OtherThis state covers errors like ALREADY_EXISTS, FAILED_PRECONDITION, DATA_LOSS, INTERNAL, INVALID_ARGUMENT, OUT_OF_RANGE, RESOURCE_EXHAUSTED, UNAUTHENTICATED or UNIMPLEMENTED. You find about these errors in {@link io.grpc.Status.Code}.
public final classResponse.Failure.Server.PermissionDeniedThe caller does not have permission to execute the specified operation.
public final classResponse.Failure.Server.UnavailableThe 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.
public final classResponse.Failure.Server.UnknownUnknown 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.
-