Hoogle Search

Within LTS Haskell 24.39 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. data PrintServerFailureInfo

    gogol-admin-directory Gogol.Admin.Directory

    Info about failures See: newPrintServerFailureInfo smart constructor.

  2. PrintServerFailureInfo :: Maybe PrintServerFailureInfo_ErrorCode -> Maybe Text -> Maybe PrintServer -> Maybe Text -> PrintServerFailureInfo

    gogol-admin-directory Gogol.Admin.Directory

    No documentation available.

  3. newtype PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    Canonical code for why the update failed to apply.

  4. PrintServerFailureInfo_ErrorCode :: Text -> PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    No documentation available.

  5. pattern PrintServerFailureInfo_ErrorCode_ALREADYEXISTS :: PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    The entity that a client attempted to create (e.g., file or directory) already exists. HTTP Mapping: 409 Conflict

  6. pattern PrintServerFailureInfo_ErrorCode_Aborted :: PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. See the guidelines above for deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE. HTTP Mapping: 409 Conflict

  7. pattern PrintServerFailureInfo_ErrorCode_Cancelled :: PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    The operation was cancelled, typically by the caller. HTTP Mapping: 499 Client Closed Request

  8. pattern PrintServerFailureInfo_ErrorCode_DATALOSS :: PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    Unrecoverable data loss or corruption. HTTP Mapping: 500 Internal Server Error

  9. pattern PrintServerFailureInfo_ErrorCode_DEADLINEEXCEEDED :: PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    The deadline expired before the 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. HTTP Mapping: 504 Gateway Timeout

  10. pattern PrintServerFailureInfo_ErrorCode_FAILEDPRECONDITION :: PrintServerFailureInfo_ErrorCode

    gogol-admin-directory Gogol.Admin.Directory

    The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide 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. For example, when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence. (c) Use FAILED_PRECONDITION if the client should not retry until the system state has been explicitly fixed. For example, if an "rmdir" fails because the directory is non-empty, FAILED_PRECONDITION should be returned since the client should not retry unless the files are deleted from the directory. HTTP Mapping: 400 Bad Request

Page 267 of many | Previous | Next