More abstractly, circuit breakers exists to allow one subsystem to fail without destroying the entire system. This is done by wrapping danger

Implement a `CircuitBreakerStorage` in local memory.

Implement a `CircuitBreakerStorage` using redis.

Listener class used to plug code to a ``CircuitBreaker`` instance when certain events happen.

When calls to a service fails because the circuit is open, this error is raised to allow the caller to handle this type of exception differently.

Tests for the CircuitBreaker class.

Tests for the CircuitBreaker class, when used as a context manager.

Tests to reproduce common concurrency between different machines connecting to redis. This is simulated locally using threads.

Tests for the CircuitBreaker class.

Implement the behavior needed by all circuit breaker states.

Define the underlying storage for a circuit breaker - the underlying implementation should be in a subclass that overrides the method this cla

Mix in to test against different storage backings. Depends on `self.breaker` and `self.breaker_kwargs`.

Tests for the CircuitBreaker class.

Tests to reproduce common synchronization errors on CircuitBreaker class.

In the normal "closed" state, the circuit breaker executes operations as usual. If the call succeeds, nothing happens. If it fails, however, the

In the "half-open" state, the next call to the circuit breaker is allowed to execute the dangerous operation. Should the call succeed, the circuit

When the circuit is "open", calls to the circuit breaker fail immediately, without any attempt to execute the real operation. This is indicated by