SASL: Last message was not SASLResponse about node-postgres HOT 7 OPEN

Hey @blechatellier - i need more code to reproduce this issue. if you can reproduce this in an isolated environment & provide the code I'm more than happy to take a look. Otherwise...not sure? Could be pg-bouncer? Or some misconfigured password somewhere?

from node-postgres.

Also having this problem - in a serverless function.

from node-postgres.

i need more code to reproduce this issue. if you can reproduce this in an isolated environment & provide the code I'm more than happy to take a look.

@jonnicholson94 - any way you could share with me some code that reproduces the problem? 🙏

from node-postgres.

@brianc sorry for the late reply, some of those issues were because of the supabase pooler terminating some connections randomly, the issue has been fixed on their side and this hasn't happened since.

from node-postgres.

I am also using supabase in my project facing this problem. I am still having this issue. Cloud you tell me how to fix this? @blechatellier

from node-postgres.

It was related to a change they did and fixed on their side supabase/supavisor#344

from node-postgres.

I've also encountered that issue in the past with an onCompletion callback from streaming an AI response that was called async after the connection was closed.

from node-postgres.