Libraries tagged by fail

Go to Download

PHP Library to read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way

Go to Download

Stop losing revenue to failed payments! Increase sales 5 to 10% by instantly retrying and approving your customers' failed payments via a backup payment processor.

Go to Download

JH M2 Core Bug Fix - Configurable products get sub-products fails when a sub-prodct is OOS

Go to Download

Uses mysqldump to dump the database out to a file when a scenario in behat fails.

Go to Download

This package provides an extension for Codeception to create Jira issues automatically when a test fails.

Go to Download

email to users when queue failed

Go to Download

Disable login after multiple failures.

Go to Download

A Laravel package that first tries to log the user against the internal database if that fails, it tries against the configured LDAP/AD server.

Go to Download

A PHP package mainly developed for Laravel to set attributes for error messages of when failing validation.

Go to Download

Standardise success and failure responses to both server and client side processing

Go to Download

Lock a user account and disable login after a given number of consecutive failed attempts.

Go to Download

PHP trait to use composite keys in your Laravel Eloquent models and does not fail on possible missing column.

Go to Download

LudicrousDB is a database class that supports replication, failover, load balancing, & partitioning, based on Automattic's HyperDB drop-in.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download