You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting 5000ms Timeout error while connecting Postgres - I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.
#636
Closed
awongCM opened this issue
Dec 30, 2023
· 1 comment
I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.
I tried downgrading it to 12.16.3 but I'm running into npm build and npm migrate cli errors due to npm versioning compatibility issues. So it's still a chicken-and-egg situation for me right now.
Can anyone shed light on the permanent resolution for it despite using the latest Postgres connector library?
The text was updated successfully, but these errors were encountered:
awongCM
changed the title
I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.
Getting 5000ms Timeout error while connecting Postgres - I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.
Dec 30, 2023
I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector: ^7.0.1.
I tried downgrading it to 12.16.3 but I'm running into npm build and npm migrate cli errors due to npm versioning compatibility issues. So it's still a chicken-and-egg situation for me right now.
Can anyone shed light on the permanent resolution for it despite using the latest Postgres connector library?
I found that I must have performed the wrong steps process of install node versioning changes between 12 and 16 on my local dev machine. So I had to redo everything from scratch again. Now the error is gone.
I have a different problem to resolve now, which is the actual db schema migration itself.
I'm using node version 16.0.0, still running into the same problem. And I'm using the latest Postgres connector:
^7.0.1
.I tried downgrading it to 12.16.3 but I'm running into npm build and npm migrate cli errors due to npm versioning compatibility issues. So it's still a chicken-and-egg situation for me right now.
Can anyone shed light on the permanent resolution for it despite using the latest Postgres connector library?
Originally posted by @awongCM in loopbackio/loopback-next#7182 (reply in thread)
The text was updated successfully, but these errors were encountered: