SASL: Last message was not SASLResponse

[gdaybrice]

Hi, I'm using node-pg in a serverless environment and I often see the following error:

Unhandled Rejection: Error: SASL: Last message was not SASLResponse
at /var/task/apps/lawy/.next/server/chunks/9840.js:1:2550
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async a.acquireConnection (/var/task/apps/lawy/.next/server/chunks/9840.js:1:58997)

I can see in code that it gets called in finalizeSession

node-postgres/packages/pg/lib/crypto/sasl.js

Line 62 in e25428c

throw new Error('SASL: Last message was not SASLResponse')

When would this error happen?

Thanks for your help.

[brianc]

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?

[jonnicholson94]

Also having this problem - in a serverless function.

[brianc]

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? 🙏

[gdaybrice]

@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.

[fengkx]

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

[gdaybrice]

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

[gdaybrice]

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.