Repository navigation
Version Issue? TimeoutOverflowWarning: ### does not fit into a 32-bit signed integer. #335
Description
What are the steps to reproduce?
Not sure.
What happens?
I see a lot of this in the logs:
(node:7) TimeoutOverflowWarning: 142244018977.92865 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(node:7) TimeoutOverflowWarning: 146813440000 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(node:7) TimeoutOverflowWarning: 119221159371.93793 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(node:7) TimeoutOverflowWarning: 125865031599.0906 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
Looking over this issue:
https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966
Looks like there may be a version issue in the docker build, but I was looking at the log to debug another issue and did not have the UI open.
What do you expect to happen?
No errors. :)
Please tell us about your environment:
Platform Docker
Image: nodered/node-red:latest (patched as of this morning)
Host: 20.04.4 LTS (Focal Fossa)
Activity
hardillb commentedon Sep 10, 2022
Have you explored the points raised in that thread?
As mentioned, this is happening because something is calling
setTimeout()with a value bigger than a 32bit integer.Nothing in the core of Node-RED will do this by default so the questions are:
settings.jsin any wayBloodBlight commentedon Sep 12, 2022
Sorry for the long delay.