`ERR_INTERNAL_ASSERTION` in `_http_server`

[XciD]

Version

v20.3.1

Platform

Linux 5.10.178-162.673.amzn2.x86_64 #1 SMP Mon Apr 24 23:34:06 UTC 2023 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

We did not succeed reproducing the bug locally, only happens on production system under high load

How often does it reproduce? Is there a required condition?

2-3 over 2M calls

What is the expected behavior? Why is that the expected behavior?

We are piping grpc call to http call using pipeline

What do you see instead?

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
  Please open an issue with this stack trace at https://github.com/nodejs/node/issues
      at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
      at new NodeError (node:internal/errors:405:5)
      at assert (node:internal/assert:14:11)
      at ServerResponse.detachSocket (node:_http_server:291:3)
      at resOnFinish (node:_http_server:973:7)
      at ServerResponse.emit (node:events:523:35)
      at onFinish (node:_http_outgoing:1005:10)
      at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
    code: 'ERR_INTERNAL_ASSERTION'

Additional information

Our pipeline code:

await pipeline(
	async function* () {
		for await (const item of iterable) {
			yield item;
		}
	},
	res,
	{ end: false }
);

await callback?.();
res.end();

[XciD]

We had some code for handling abort request that broke the internal:

req.on("close", () => {
	if (req.readableAborted) {
		/// ^ HTTP Request has been aborted, express doesn't send a finish event so we fake one
		res.statusCode = 499;
		res.emit("finish");
	}
});

Once the code removed, no more issue.