-
Notifications
You must be signed in to change notification settings - Fork 303
Occasional TimeoutNegativeWarning: -81612681.54468305 is a negative number.
#1061
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
Comments
same issue DId u know is there any bad thing which happends because of it? This happened in Bun too |
We recently update from node 22 to node 24 and from "postgres": "^3.4.5" to "postgres": "^3.4.7" and face the same issue. |
I use Bun and got the same issue But after many times it looks like everything works fine |
I don't think there is any negative impact because of this warning, it's just noisy. A simple fix could be setTimeout(connect, Math.max(closedDate ? closedDate + delay - performance.now() : 0, 0)) |
getting this in adonisjs with a postgres db
|
I'm running a Node.js app in K8s. Occasionally (every other day) I get this warning:
(with varying negative timeout values)
The stacktrace always points to the reconnect function here https://github.com/porsager/postgres/blob/master/src/connection.js#L353
Unfortunately I don't know how to reproduce this issue. On first glance it looks like it happens directly after the app boots up.
The text was updated successfully, but these errors were encountered: