imaricodes
commented
1 year ago Further convinced the time out is an issue we have to handle... see this phind.com explanation -handle when connection is idle for x amount of time -handle when connection fails (reconnect attempts) -handle when connection times out (set amount of time, what to do when time out) -better handle connection issues in general (error handling)
This is the first time I've noticed the error. It occurred while I was working on the google recaptcha. I'm not sure the error is related to the reCaptcha because I'm not doing anything with the postgres server. It may be some timeout setting in the postgres server. It does cause the server to crash.
Can you try to recreate the error... maybe by leaving the app idle for some amount of time? I need to further diagnose. I would suggest checking out the new recatcha (oops spelled wrong) branch locally to see if it's something in that new code.
This is what Phind.com says about the error.
this is the error on server console:
Error: Connection terminated unexpectedly at Connection. (/Users/imarichildress/Documents/dev-projects/time-distance-tracker-project/time-distance-tracker/node_modules/pg/lib/client.js:132:73)
at Object.onceWrapper (node:events:628:28)
at Connection.emit (node:events:514:28)
at Socket. (/Users/imarichildress/Documents/dev-projects/time-distance-tracker-project/time-distance-tracker/node_modules/pg/lib/connection.js:63:12)
at Socket.emit (node:events:526:35)
at TCP. (node:net:323:12)
at TCP.callbackTrampoline (node:internal/async_hooks:130:17)