Bug Fix: Remove I/O from Redlock.__repr__() and NextId.__repr__()
When the Redis connection pool is exhausted, the Redis client throws ConnectionErrors. Then the Sentry SDK tries to record the tracebacks. If you have a Redlock or a NextId anywhere in those tracebacks, then the Sentry SDK calls repr() on those objects. And if those objects' .__repr__()s try to talk to Redis, then the client throws nested ConnectionErrors.
So don't talk to Redis from Redlock.__repr__() or NextId.__repr__().
What's Changed
Full Changelog: v1.3.2...v1.3.3