Premature close

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the bug has not already been reported

Fastify version

3.27.4

Plugin version

4.0.1

Node.js version

16.13.1

Operating system

macOS

Operating system version (i.e. 20.04, 11.3, 10)

12.0.1

Description

Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
  at new NodeError (node:internal/errors:371:5)
  at Duplexify.onclose (node:internal/streams/end-of-stream:135:30)
  at Duplexify.emit (node:events:402:35)
  at Duplexify.emit (node:domain:475:12)
  at Duplexify._destroy (/Users/gajus/Documents/dev/contra/contra-web-app/node_modules/duplexify/index.js:199:8)
  at /Users/gajus/Documents/dev/contra/contra-web-app/node_modules/duplexify/index.js:182:10
  at processTicksAndRejections (node:internal/process/task_queues:78:11)

Steps to Reproduce

This appears to happen when request is aborted while still serving the file.

Expected Behavior

Should produce a warning, but not an uncaught error.

[ilya-adnymics]

Too late to the party, but Google sent me here, so I’ll post a comment in case someone else would end up here as well.
Got the same error after migrating to fastify 4 and @fastify/compress 6. I didn’t want to remove @fastify/compress as I find it super nice (although the error was gone after I tried commenting it out 🤷‍♂️). What fixed it for me is following this instructions from fastify Migration guide:

In some situations, like when a response is sent asynchronously or when you’re just not explicitly returning a response, you’ll need to return the reply argument from your router handler.

So basically repace

  ...
  reply.send(page)
  return

with

  return reply.send(page)

After this, my requests started working, compression is working as well.

[SimenB]

https://github.com/fastify/fastify/releases/tag/v3.29.1 has the backport 🎉