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
(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.
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:
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)
The text was updated successfully, but these errors were encountered: