Fix websocket panic issue

[timmo001]

Fixes #3431

A WebSocket panic due to concurrent writes was addressed by implementing per-connection write synchronization.

Key changes include:

• A new connectionInfo struct was introduced in backend/websocket/websocket.go, embedding a *websocket.Conn and a sync.Mutex for write protection.
• The WebsocketServer.connections map was updated to store map[string]*connectionInfo instead of map[string]*websocket.Conn.
• The SendMessage function in backend/websocket/messages.go was refactored to accept a *connectionInfo and acquire its writeMux before calling conn.WriteJSON(), ensuring thread safety for writes to that specific connection.
• All call sites of SendMessage and connection management functions, including AddConnection, RemoveConnection, handleMessages, BroadcastModuleUpdate, and SendError in backend/websocket/handlers.go and backend/websocket/messages.go, were updated to utilize the new connectionInfo structure.

This approach prevents concurrent writes to the same WebSocket connection, resolving the panic, while allowing concurrent writes to different connections for optimal performance.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
system-bridge	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 28, 2025 9:24am

[timmo001]

bugbot run

[timmo001]

bugbot run

[timmo001]

bugbot run