1
83%
master: 83%

Ran 07 Apr 2026 02:32AM UTC

Files 54

Run time 1s

Badge

Embed ▾

Committed 07 Apr 2026 02:29AM UTC coverage: 82.86% (+0.04%) from 82.818%

Job # 24061322700.1

Build Type

Pull #414

github

Committed by

shiv3

Commit Message

fix: prevent deadlock in websocket write during connection cleanup

When many connections disconnect simultaneously (e.g. cluster autoscaler
pod restart), a deadlock can occur between WriteManual/Close and cleanup:

1. WriteManual holds w.mutex.RLock and blocks on outQueue send (buffer full,
   writePump no longer reading because it exited to call cleanup)
2. cleanup waits for w.mutex.Lock, which requires all RLock holders to release
3. Neither can proceed -> deadlock

Additionally, server.Write held s.connMutex.RLock during the entire w.Write
call. If w.Write blocked, it prevented all handleDisconnect calls (which need
s.connMutex.Lock) across all connections, causing cascading "already exists"
errors when charge points attempted to reconnect.

Fix:
- Add a done channel to webSocket, closed at the start of cleanup
- Use select in WriteManual and Close to abort when done is signaled
- Release s.connMutex.RLock in server.Write before calling w.Write

Pull Request Pull Request #414: fix: prevent deadlock in websocket write during connection cleanup

Coverage Stats

3732 of 4504 relevant lines covered (82.86%)

18.18 hits per line

lorenzodonini / ocpp-go / 24061322700 / 1
83%
master: 83%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 24061322700.1

lorenzodonini / ocpp-go / 24061322700 / 1 83% master: 83%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 24061322700.1

lorenzodonini / ocpp-go / 24061322700 / 1
83%
master: 83%

README BADGES
x