Libraries tagged by exceptions
nubitio/platform
2286 Downloads
Platform foundation for Nubit Symfony apps: domain exceptions, tenant contracts, feature gates, quota contracts, messenger middleware, cache/file/export helpers.
nowo-tech/beacon-php
922 Downloads
Framework-free PHP client for Beacon (nowo error tracking): DSN, Envelope ingest over PSR-18 or Symfony HttpClient, scope and breadcrumbs, scrubbing, error / exception / fatal handlers, Monolog handler.
niladam/livewire-ban
3063 Downloads
Automatically ban IP addresses that trigger Livewire exceptions no legitimate browser session can produce.
nicodev/asserts
37030 Downloads
List of traits that make assertions and throw Exception if assertion fails.
myparcelcom/json-api
83635 Downloads
MyParcel.com shared library with JSON API related exceptions, interfaces, traits and utility classes.
luyadev/luya-module-errorapi
21817 Downloads
To create strong and secure website its important to know all exceptions before your customer knows the exceptions and to make sure the exception happends only once.
lossik/device-communication
4187 Downloads
Transport-independent contract for RouterOS clients: commands, queries, results, a client API and typed exceptions
lookout/tracing
1205 Downloads
Distributed tracing, sampled performance spans (limits, Laravel collectors), optional browser RUM beacons, breadcrumbs, structured logs and custom metrics ingest, exception reporting with enrichment pipeline, cron check-ins, and profiling ingest for Bilge.
laravel-enso/sentry
26845 Downloads
Sentry exception handling for Laravel Enso
konfig/snaptrade-php-sdk
26139 Downloads
Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.
k8s/core
20395 Downloads
A set of needed interfaces, classes and exceptions for the k8s-client, k8s-api, and the websocket adapters.
jonaspardon/wn-pulse-plugin
550 Downloads
Laravel Pulse for Winter CMS: routing, backend access, Winter users and exceptions wired up
jield-webdev/laminas-psr-doctrine-error-hero-module
11909 Downloads
A Hero for your Laminas and Mezzio application to trap php errors & exceptions
ideatic/dump
4235 Downloads
Displays information about any PHP variable, class or exception.
hampel/json
107459 Downloads
A simple wrapper for json_encode and json_decode with exception based error handling