ksmithandClaude Sonnet 5 850d9ec0fa Supervise the broadcast listener so it recovers from a dropped Redis connection (#76) ...

The previous fix hardened listen() against a single bad message, but a
connection-level failure (Redis restarting, a network blip) raises from
the async-for iteration itself, outside that guard, and killed the
task permanently and silently -- HTTP/REST and login kept working fine
since neither touches it, but live message delivery was gone for every
room and every user on the affected process until a manual restart.

Confirmed live in production after an OS update restarted Redis:
PUBSUB NUMPAT showed zero pattern subscriptions across all 4 gunicorn
workers, meaning every one of them had lost its listener with nothing
to bring it back.

Broadcaster.run_forever() now supervises listen(), restarting it with
exponential backoff (capped at 30s, reset after a stable 60s+ run) on
any failure, while still letting a genuine shutdown (task
cancellation) propagate immediately instead of being treated as just
another retry.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-26 15:19:59 -06:00

..

__init__.py

Phase 1: auth, room CRUD, WebSocket chat, PWA frontend

2026-08-13 20:01:17 -06:00

broadcaster.py

Supervise the broadcast listener so it recovers from a dropped Redis connection (#76)

2026-09-26 15:19:59 -06:00

chat.py

Add WS heartbeat and harden broadcast against dead sockets (#76)

2026-09-23 12:37:58 -06:00

connection_manager.py

Add WS heartbeat and harden broadcast against dead sockets (#76)

2026-09-23 12:37:58 -06:00

focus_presence.py

Fix desktop messages not appearing live until refocus (#59)

2026-08-19 18:08:04 -06:00

global_presence.py

Add presence indicators and a manual "appear offline" override (#36)

2026-08-16 15:39:56 -06:00

presence.py

Phase 5: Redis pub/sub for horizontal scaling

2026-08-14 07:13:06 -06:00