Version Issue? TimeoutOverflowWarning: ### does not fit into a 32-bit signed integer.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, node.js
- Domain
- devops, infrastructure
Research direction
Start by reviewing the nodered/node-red:latest Docker image version and the linked Node-RED discussion about TimeoutOverflowWarning. Reproduce or inspect logs in the reported Docker and Ubuntu environment, then identify whether the warning comes from the image or an underlying dependency. Done means the source is confirmed and the image no longer emits these warnings in the reported scenario.
Written by the indexing model from the issue text.
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)
- Dominant language
- Shell
- Stars
- 540
- Forks
- 434
- Avg merge
- 24m
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from node-red/node-red-docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
node-red/node-red-docker#536 ·
-
node-red/node-red-docker#522 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
node-red/node-red-docker#513 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
node-red/node-red-docker#510 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
node-red/node-red-docker#493 · 13 comments ·
All issues in node-red/node-red-docker
Similar issues
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
Feature Request: Add ability to load custom environment variables in linux-exec-server-installer.sh Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/vscode-remote-release#11867 ·
-
AuTest Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/trafficserver#13714 ·
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
vllm-project/agentic-api#358 · 1 comment ·