Libraries tagged by failures

WordPress must-use plugin that sends mail through Amazon SES with an IAM role, so no SMTP credentials are stored and no send failures pass silently.

Go to Download

Real-time queue job monitoring, debugging, and failure analysis for Laravel

Go to Download

Queue idempotency, retry, failure, scheduling, locking, and deployment conventions.

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.41) is used. For example, calling `/info` is the same as calling `/v1.41/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 [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (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

A Laravel package to monitor queue failures and send notifications based on thresholds and time windows.

Go to Download

The "HTTP Status Code Abstraction" project is a PHP 8-based initiative aimed at simplifying the management and usage of HTTP status codes by introducing ENUM support. HTTP status codes are integral to web development, providing vital information about the success or failure of HTTP requests and responses. However, managing and referencing these status codes in a clear and organized manner can often be challenging. This project seeks to address this challenge by leveraging PHP 8's ENUM feature.

Go to Download

Laravel package for AMQP message handling with automatic retry, dead letter queue, and failure management

Go to Download

Safe type coercion for PHP – returns null on failure, no exceptions, no dependencies.

Go to Download

A return type for operations that can fail — make every failure visible, typed, and impossible to ignore

Go to Download

Run symbiote/queuedjobs, and ping a Healthchecks.io endpoint for start/finish/failure

Go to Download

Library enabling you to introduce some failure into your application

Go to Download

Retry Loop is tiny class for widely used concept of retry on failure code

Go to Download

Resilient Client is a PHP package designed to implement a circuit breaker pattern to enhance stability and prevent cascading failure requests

Go to Download

Instruments Drupal cron execution and sends results to the New Relic Event API for alerting on failures, slow runs, and missing runs.

Go to Download

Laravel Queue Monitoring Package - Tracks job execution, progress, and failures automatically

Go to Download