Diagram sources

Original files and free editing for our documentation contributions. No account or backlink required. These are independent contributions; inclusion here does not imply project approval.

Tenacity runs before, then the attempted function. If the retry predicate accepts the outcome, after runs, wait computes the delay, and stop chooses exhaustion or before_sleep followed by sleep and the next attempt. An outcome not selected for retry returns or raises.

tenacity · Version 1

Tenacity retry callback order

View source and edit →

Worker processing runs pre_execute, task execution, optional on_error and post_execute. Result storage precedes post_save, which runs only after successful storage. NoResultError skips storage.

taskiq · Version 1

Taskiq worker middleware and result storage

View source and edit →

The dependent job waits for both prerequisite jobs. Successful completion of every required dependency permits enqueueing; one completed prerequisite is insufficient.

rq · Version 1

RQ jobs with multiple dependencies

View source and edit →

Queueing locks reject admission of another matching pending job, while execution locks serialize matching job execution. The two checks govern different stages of the job lifecycle.

procrastinate · Version 1

Procrastinate queueing locks and execution locks

View source and edit →

User depends on Name and Description. Description also depends on Name. Directed links show the dependencies used by the documented User construction example.

injector · Version 1

Injector example dependency graph

View source and edit →

A shielded inner cancel scope protects its work from outer cancellation while active. Cancellation initiated within the inner scope still applies. Leaving the shield restores the surrounding cancellation context.

anyio · Version 1

AnyIO cancellation shielding

View source and edit →

Caught errors handled without rethrowing stay with custom middleware. Otherwise Koa snapshots headers and writability, emits the error event, then uses that saved state to gate its default response.

koa · Version 1

Koa middleware error handling and default response

View source and edit →

One connection watches and reads a key. Another connection changes it before MULTI and EXEC. Redis returns a null EXEC reply, so none of the queued writes execute; Node Redis exposes this as WatchError.

node-redis · Version 1

Redis WATCH conflict between two connections

View source and edit →

The owner selects dirty schema-indexed component fields, batches entity updates and sends them through its adapter. The receiving adapter routes each networkId, then the remote component applies or interpolates matching schema fields.

networked-aframe · Version 1

Networked-Aframe periodic component synchronization

View source and edit →

Two PUBLISH packets arrive together. MQTT.js emits message for packet 1 and invokes handleMessage. Callback 1 gates PUBACK 1 and handling packet 2; packet 2 follows the same event, handler, callback and acknowledgement sequence.

mqttjs · Version 1

MQTT.js callback-gated QoS 1 message handling

View source and edit →

Creation leads to a render pass and a mounted component. Messages call update; changed properties call changed. Handlers can request another render or return without requesting one. Unmounting calls destroy before DOM detachment.

yew · Version 1

Yew client-side component lifecycle and render requests

View source and edit →

Server load data feeds universal load during SSR and is serialized into the initial HTML. The browser passes that original server data to universal load again during hydration, reusing captured fetch responses. The page receives the universal load result.

sveltekit · Version 1

SvelteKit server and universal load data during SSR and hydration

View source and edit →

A restore attempt first passes the call throttle, computes a cutoff using the scanning worker's visibility timeout, and acquires the shared restore mutex. It selects due delivery tags and restores each selected tag. Throttled attempts, an unavailable mutex or an empty selection do not requeue messages.

kombu · Version 1

Kombu Redis unacknowledged message restore sweep

View source and edit →

The parent awaits nursery.start for a trio.serve_tcp child. The child binds listening sockets, then calls task_status.started(listeners). Only then does the parent receive the listeners and connect to a returned port. The child continues serving after the readiness signal.

trio · Version 1

Trio service startup readiness handshake with nursery.start

View source and edit →

Each event belongs to one tournament. Events and teams have a many-to-many relationship represented by event_team rows with event_id and team_id foreign keys. Reverse events and participants relations are Python accessors, not extra table columns. The main id fields are primary keys; junction pairs are unique without a declared primary key.

tortoise-orm · Version 1

Tortoise ORM example models and generated SQLite relationships

View source and edit →

node-redis · Version 2

Redis WATCH conflict between two connections

View source and edit →