Skip to content
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

TimeoutOverflowWarning when building the site #2442

Closed
XhmikosR opened this issue Aug 21, 2019 · 2 comments · Fixed by #2500
Closed

TimeoutOverflowWarning when building the site #2442

XhmikosR opened this issue Aug 21, 2019 · 2 comments · Fixed by #2500

Comments

@XhmikosR
Copy link
Contributor

When building the site with npm run build I get:

TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.

I'm on Node.js 12.8.1 on Windows 10 64-bit but it happens on Travis too. It's just not shown because currently the build script is inside tap. You can see it on my fork though https://travis-ci.org/XhmikosR/nodejs.org/builds/574910707#L216

IMO we should run npm run build in an npm script and not inside tap.

@XhmikosR
Copy link
Contributor Author

XhmikosR commented Sep 2, 2019

I managed to trace this down to


C:\Users\xmr\Desktop\nodejs.org>set NODE_OPTIONS=--trace-warnings

C:\Users\xmr\Desktop\nodejs.org>npm start

> nodejs.org@ start C:\Users\xmr\Desktop\nodejs.org
> npm run serve


> nodejs.org@ serve C:\Users\xmr\Desktop\nodejs.org
> node server.js

[metalsmith] build/static started
[metalsmith] build/layouts started
Server running at http://localhost:8080/en/
(node:2584) TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.
    at getTimerDuration (internal/timers.js:366:13)
    at ClientRequest.setTimeout (_http_client.js:760:11)
    at Req._send (C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:138:29)
    at C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:50:21
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
(node:2584) TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.
    at getTimerDuration (internal/timers.js:366:13)
    at ClientRequest.setTimeout (_http_client.js:760:11)
    at Req._send (C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:138:29)
    at C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:50:21
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
(node:2584) TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.
    at getTimerDuration (internal/timers.js:366:13)
    at ClientRequest.setTimeout (_http_client.js:760:11)
    at Req._send (C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:138:29)
    at C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:50:21
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
(node:2584) TimeoutOverflowWarning: 4294967296000 does not fit into a 32-bit signed integer.
Timer duration was truncated to 2147483647.
    at getTimerDuration (internal/timers.js:366:13)
    at ClientRequest.setTimeout (_http_client.js:760:11)
    at Req._send (C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:138:29)
    at C:\Users\xmr\Desktop\nodejs.org\node_modules\hyperquest\index.js:50:21
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
[metalsmith] build/layouts finished: 674.879ms
[metalsmith] build/en started
[metalsmith] build/en finished: 6396.127ms
C:\Users\xmr\Desktop\nodejs.org>npm ls hyperquest
nodejs.org@ C:\Users\xmr\Desktop\nodejs.org
`-- [email protected]
  `-- [email protected]
    `-- [email protected]

So, this needs node-version-data to bump jsonist. @rvagg any chance you could take care of this?

@rvagg
Copy link
Member

rvagg commented Sep 5, 2019

Published [email protected] which should address this. Thanks for all the diligence around this repo @XhmikosR, good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants