net::ERR_INCOMPLETE_CHUNKED_ENCODING in node v8.0 + chrome 58.0.3029.110

[Rayraegah]

Seeing this error http://localhost:4000/__webpack_hmr net::ERR_INCOMPLETE_CHUNKED_ENCODING in browser console after upgrading to node v8. As a result, code injection fails for certain updates.

UPDATE:
Here's what I've tried and known to work

• About 15 seconds after launching application, this error pops up in the console
• About 30 ~ 45 seconds later, hmr works again
• And then, it randomly breaks. Haven't been able to determine the criteria upon which it fails
• hmr was stable in node v7

reference: egoist/poi#179

[egoist]

Here's a minimal repro:

https://gist.github.com/egoist/55fed736c70eeb74a238a738f9f5ed13

[brudil]

From what I can tell, node is killing the request due to a timeout.

Edit: I think it might be this: nodejs/node#2534. So there is now a 5s keep-alive timeout that can be set via keepAliveTimeout.

It looks like keepAliveTimeout needs to be set on the server before any requests - as I understand Express middleware works on requests.

const server = app.listen(4000, () => {
  server.keepAliveTimeout = 0;
});

Using a heartbeat of 5s or less also works.

[glenjamin]

Is there anything we can do per-request?

Requiring server changes for a middleware is a bit annoying.

Maybe we should just make the default heartbeat 4 seconds instead?

[brudil]

Yeah, perhaps a lower default and a print a warning if the heartbeat is lower than keepAliveTimeout?

[jharris4]

I just started encountering the same issue after upgrading to Node 8.

@brudil thanks for the fix, setting the server's keepAliveTimeout to 0 resolved the issue for me.

[jptissot]

Seems to work fine on node 8.1.1

[antenando]

I can confirm it's working with node 8.1.1 as well

[michaeljonathanblack]

Also confirmed! 💃

Just gotta update to 8.1.1 and it's golden.

[glenjamin]

Anyone know what changed in core to fix this for us?

[Rayraegah]

Anyone know what changed in core to fix this for us?

@glenjamin it's both nodejs/node#13435 + nodejs/node#13391 and the one @brudil pointed out in his reply its nodejs/node#2534. They're all pointing to the same issue.

[glenjamin]

Cheers for the link, read through those and it looks like nodejs/node#13549 was the fix.

Gonna call this issue closed

[crifan]

upgrade node to latest version(9.0.0):

node -v
sudo npm cache clean -f
sudo n stable
node -v

also fixed for me.

[olei]

The problem has been solved. thx