Failed to pipe response after upgrade next.js to v15.1.2 (from v14.x.x)

[studentIvan]

Summary

Site looks working well, nothing fall from quick look, but in the AWS console there are a lot of spammy errors with no any information:

15:43:02 ⨯ [Error: failed to pipe response] {
15:43:02 [cause]: [TypeError: readable.pipeTo is not a function]
15:43:02 }
15:43:06 ⨯ [Error: failed to pipe response] {
15:43:06 [cause]: [TypeError: readable.pipeTo is not a function]
15:43:06 }

Anybody can help me with how to debug it or at least what is the direction I should seek this problem?

Additional information

node v18.18.0
next v15.1.2
running on aws (flightcontrol)
using redis custom cache handler
NO api using
custom middleware is using

using run command: yarn next start --keepAliveTimeout 70000 -p 8080

Example

No response

[vitaliemiron]

same question

[justinadkins]

@studentIvan Do you happen to be using a patched version of https://github.com/caching-tools/next-shared-cache? I was seeing this same issue and I believe it was resolved with this change.

[studentIvan]

looks like a solution, thanks

[erwanriou]

Right, but there is no release of the new version yet right? Do you know when this PR will be merged?

[justinadkins]

I do not, I've been running a patched version and addressing issues as they come up in my use case.

[erwanriou]

Hmm then i will wait. I will migrate to 15 once we have this PR done. I guess there is still a lot of backward compatibility to cover.