Martin Connor

Results 37 comments of Martin Connor

Also I'm running this with a serverless db in AWS, so maybe when the server on which this db is running gets closed down then pg-boss throws this error?

Will do, thank you @timgit! Love the lib btw Edit: The shim suggested in #365 did not work, but I also think their problem was slightly different from mine.

Looks like it's happening in 9.0.0 too: ``` node:internal/errors:465 ErrorCaptureStackTrace(err); ^ Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({ message: 'Connection terminated unexpectedly (Queue: __state__completed__onCompleteFtw, Worker: e5e396aa-7aaa-47b2-8c4c-200fa791ca22)', stack: 'Error: Connection terminated unexpectedly (Queue:...

I've been calling .start and .subscribe in the app.listen callback: ``` app.listen(3039, async () => { console.log('listening on 3039') await boss.start(); await boss.subscribe(`demucs-${process.env.APP_ENVIRONMENT}`, separateAudio); }) ``` Where do I call...

Alright now I'm calling boss.start(0 right before creating and starting a job, and boss.stop at the end of the `.onCompelte` callback, but I'm now getting this error about destructuring properties:...

Hey Tim, thanks for the help. I really appreciate it. As for your points: 1.) I do have an error handler. You can see it where I am instantiating the...

Thanks Tim, that's helpful info. I really feel like the problem is with some db config settings then. I have an RDS instance running on AWS. I will investigate the...

Turns out this is a known issue with node-postgres, which pg-boss appears to use under the hood: https://github.com/brianc/node-postgres/issues/2112 Takeaways: probably has to do with timeout settings of infrastructure provider. Might...

@KPouianou sorry, not yet. What is your db running on? AWS?

HI @timgit, could you please confirm that pg-boss does not allow the `keepAlive` option to be set when configuring pg-boss' connection to the database via node-postgres? Docs on pg-boss' connection...