Commit577a2f0

committed

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]

1 parent8027c0f commit577a2f0Copy full SHA for 577a2f0

File tree

1 file changed

-2

lines changed

src/PostgresWebsockets
- Middleware.hs

1 file changed

-2

lines changed

`‎src/PostgresWebsockets/Middleware.hs`

Lines changed: 1 addition & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -111,8 +111,7 @@ wsApp Context {..} pendingConn =`
`111`	`111`	`when (hasWrite mode)$`
`112`	`112`	`notifySession conn sendNotification chs`
`113`	`113`
`114`		`- waitForever<- newEmptyMVar`
`115`		`- void$ takeMVar waitForever`
	`114`	`+ void$ forever$ threadDelaymaxBound`
`116`	`115`
`117`	`116`	`-- Having both channel and claims as parameters seem redundant`
`118`	`117`	`-- But it allows the function to ignore the claims structure and the source`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit577a2f0

File tree

1 file changed

1 file changed

`‎src/PostgresWebsockets/Middleware.hs`

0 commit comments