myndzi
myndzi
Same thing, different error. ETIMEDOUT would be "settings were wrong" or possibly "network connectivity bombed while this thing tried to start up"
Any news on this? If it's not an initial time out it might also be related to #14.
Can you clarify: does this happen when you start your application if the DB is inaccessible, or does this happen after your application has been running and working, but loses...
What version of pool2 is currently installed? (`npm ls pool2`) Also, what version of knex?
Ah, I think I see the problem. acquireRawConnection is returning a promise, however the error handler is attempting to destroy the `connection` object. Alternately, it might be trying to release...
Refused the first time after a long rest = a timeout; pool2 was designed to throw an error if the first attempted connection fails. You could update to 1.2.0 to...
Apologies, I've gotten quite busy at work and didn't do what I said I would do to look into this. I would appreciate it if you could tell me if...
If it's crashing, then it's not being caught at all.. but the "Knex:Error" part gets added by knex so it must obviously be captured...? I recommend in the short term...
Okay! I managed to reproduce the error scenario by hooking into net.Socket and "eating" a selected write while emitting an error on the socket object. However, the application does not...
We can see the double release here: ``` knex:client acquiring connection from pool: __knexUid1 +0ms knex:query select 1 +1ms write 2 pool2 Ungracefully destroying resource (id=0) +3ms pool2 Attempting to...