In lacinia-pedestal, the default timeout for the websocket server is 30s, however, there appears to also be a timeout in jetty used by pedestal of 30s. So in its default configuration its a bit race’y whether your websocket gets closed by jetty (if the subscription go loop is slightly too slow). Would it make sense to change the default / configure jetty to not have a timeout / …?
I wish we were eating our own dogfood here. Yes, a shorter timeout makes perfect sense.
It’s a bit unfortunate how it is now; using the default timeout causes you to get a websocket server that kills its client connection every few keep alives :’).