Closed flip111 closed 1 year ago
I found out that if connect
works successfully then this error still occurs .. must be something else then.
I'm going to close this as i don't believe any longer there is a problem with resource-pool. Even though i'm still wondering if MonadError is supported. Sorry to bother
I used the pool together with hasbolt.
Pool Pipe
is constructed using this function https://hackage.haskell.org/package/hasbolt-0.1.6.2/docs/Database-Bolt.html#v:connect which can throw an error here https://github.com/zmactep/hasbolt/blob/0c233896b59dbb4a7baa18ead3314a8c933472af/src/Database/Bolt/Connection/Pipe.hs#L115when the error is thrown the
withResource
function hangs. I guess there was some lazyness somewhere because when i modify the code like thisand
the last trace statement never happens and the code hangs on show