Alex Jbanca 539236d791

fix: SetClosing no longer holds SubscriptionDetails lock across a potentially blocking channel send ...

- SetClosing(): send moved out of the s.Lock() critical section, performed via select/default to tolerate stalled receivers and concurrent CloseC that may have closed the channel.
- Closing channel: changed from unbuffered (make(chan bool)) to buffered size 1 (make(chan bool, 1)) in NewSubscription. Pairs with the s.Closed guard (single send per subscription), so the sender never parks.

2026-04-21 10:25:00 +03:00

..

cliutils

chore: remove bridging topics feature (#949)

2023-12-09 13:59:35 -04:00

metrics

fix: return error in relay publish if exceeding max-msg-size (#939)

2023-12-01 06:53:28 +05:30

persistence

feat: log error and stacktrace when panic in goroutine (#1225)

2024-09-25 17:15:20 +08:00

tools

chore: switch to Google's Protobuf library

2023-02-16 11:37:59 -04:00

try

feat: Implement logic for publish from node

2021-12-07 14:32:02 +01:00

v2

fix: SetClosing no longer holds SubscriptionDetails lock across a potentially blocking channel send

2026-04-21 10:25:00 +03:00