Repository navigation
Version Issue? TimeoutOverflowWarning: ### does not fit into a 32-bit signed integer. #335
Description
Activity
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:
- Have you modified the
settings.jsin any way - Have you set the inject or trigger node to large (multi week/month) timeout values?
- What extra nodes are you using?
- Have you modified the
Sorry for the long delay.
- Not that I recall, the install has been in place for years though.
- Not that I know of, I didn't realize the timeout could be adjusted. I think the longest time value I have in any node is a 1 hour trigger and a 30 minute repeat.
- A fair number, not all of them are actively being used:
- node-red - 3.0.2
- node-red-contrib-countdown-2 - 1.4.2
- node-red-contrib-discord-advanced - 2.3.1
- node-red-contrib-google-smarthome - 0.3.7
- node-red-contrib-home-assistant-llat - 0.3.10
- node-red-contrib-spotify - 0.1.4
- node-red-contrib-stackhero-influxdb-v2 - 1.0.4
- node-red-contrib-tesla - 2.0.0
- node-red-contrib-unifi-os - 0.7.1
- node-red-contrib-zigbee2mqtt-devices - 0.19.5
- node-red-node-base64 - 0.3.0
- node-red-node-email - 1.15.1
- node-red-node-feedparser - 0.2.2
What are the steps to reproduce?
Not sure.
What happens?
I see a lot of this in the logs:
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)