rcourtman d30d76bb92 Fix P1: Add shutdown mechanism to WebSocket Hub ... Fixed goroutine leaks in WebSocket hub from missing shutdown mechanism: Problem: 1. Hub.Run() has infinite loop with no exit condition 2. runBroadcastSequencer() reads from channel forever 3. No way to cleanly shutdown hub during restarts or tests Solution: - Added stopChan chan struct{} field to Hub - Initialize stopChan in NewHub() - Added Stop() method that closes stopChan - Modified Run() main loop to select on stopChan - On shutdown: close all client connections and return - Modified runBroadcastSequencer() from 'for range' to select - Changed from: for msg := range h.broadcastSeq - Changed to: for { select { case msg := <-h.broadcastSeq: ... case <-h.stopChan: ... }} - On shutdown: stop coalesce timer and return Shutdown sequence: 1. Call hub.Stop() to close stopChan 2. Both Run() and runBroadcastSequencer() exit their loops 3. All client send channels are closed 4. Clients map is cleared 5. Pending coalesce timer is stopped Impact: - Enables graceful shutdown during service restarts - Prevents goroutine leaks in tests - Allows proper cleanup of WebSocket connections - No more orphaned broadcast sequencer goroutines		2025-11-07 10:20:26 +00:00
..
concurrency_test.go	Fix settings security tab navigation	2025-10-11 23:29:47 +00:00
hub.go	Fix P1: Add shutdown mechanism to WebSocket Hub	2025-11-07 10:20:26 +00:00
hub_concurrency_test.go	refactor: use strconv.Itoa instead of string(rune()) in test	2025-10-20 15:12:14 +00:00