-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when using transaction timeout #471
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
I'm experiencing this issue ! 😕 I'm in the process of upgrading a node project running with Node 10, bringing it to the latest version of Node (v14.17.3). I have some behaviour tests (endpoint tests) to make sure that I didn't break anything. When I execute my tests, at random points (after at least 5 seconds, so many requests) my backend crashes with the following error:
I have no idea what is happening because the error ocurrs at random places. Help, please !!!
|
@cluis13915 @nicoskk I am facing the same issue, have you came across any solution for this? |
@prachitin I just avoided setting the |
Since version 5.1.0 which updates its dependencies (loopback-connector: ^5.0.0) It will give this error with loopback 3. The transaction is created with loopback-connector@5 for loopback-connector-postgresql, but loopback will use loopback-connector@4 which is modified by this line https://github.com/loopbackio/loopback-datasource-juggler/blob/3.x/lib/transaction.js#L117 The solution I found was to install loopback-connector as a direct dependency |
Steps to reproduce
loopback-connector-postgresql version is 5.3.0
node version is v14.1.0
Current Behavior
aftersome time, app crashes with the following error
The text was updated successfully, but these errors were encountered: