It seems that without the notifySession being open in the middleware, the runtime detects the waiting on the MVar as an infinite wait. Which although true, it's useful to relay read messages and the connection will be closed by warp when the client disconects.

This should fix [#105]

Author: diogob

src/PostgresWebsockets/Middleware.hs

@@ -111,8 +111,7 @@ wsApp Context {..} pendingConn =
         when (hasWrite mode) $
           notifySession conn sendNotification chs
 
-        waitForever <- newEmptyMVar
-        void $ takeMVar waitForever
+        void $ forever $ threadDelay maxBound
 
 -- Having both channel and claims as parameters seem redundant
 -- But it allows the function to ignore the claims structure and the source