loop/notifications
Slyghtning 7a137df098
notifications: queue blocking fanout
Some notification types are work requests and must not be dropped when a
subscriber channel is temporarily full. Sending them synchronously from the
global notification handler can stall the stream while a slow subscriber holds
back reads.

Add a per-subscriber queue for blocking notification classes and deliver those
notifications from a worker tied to the subscriber context. Keep direct sends as
the fallback for subscribers that do not need queued delivery.

Use the queued path for static loop-in sweep requests and unfinished swap
notifications, and fix subscriber removal to compare channel identity now that
subscribers contain function fields.
2026-05-22 11:22:45 +02:00
..
log.go multi: update lnd compile-time dependency to v0.19.0 2025-03-10 22:59:49 +01:00
manager.go notifications: queue blocking fanout 2026-05-22 11:22:45 +02:00
manager_test.go notifications: queue blocking fanout 2026-05-22 11:22:45 +02:00