[Bug?]: Seeing 500s due to ERR_STREAM_PREMATURE_CLOSE after upgrade to 7.x
What's not working?
Never really saw ERR_STREAM_PREMATURE_CLOSE 500s in our logs ever before. After the upgrade to 7.x, on our deployed app, I see this issue constantly:
Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
at Readable.onclose (node:internal/streams/end-of-stream:154:30)
at Readable.emit (node:events:518:28)
at emitCloseNT (node:internal/streams/destroy:147:10)
at process.processTicksAndRejections (node:internal/process/task_queues:81:21)Initially saw this issue (500s accompanied with this error) happen with our end to end tests, and then with some customers. Was eventually able to reproduce it, I kid you not, by just refreshing the page a few times. Can't repro this locally because presumably the stream interruption can't be reproduced without a certain amount of latency expected in an actual deployed scenario.
I don't think we should have to handle 500s due to this specific issue, though please advise if this is expected behavior. This seems to be a lower level issue being bubbled up as a 500.
How do we reproduce the bug?
Deploy app + refresh a page with some graphql queries (presumably) a bunch of times
What's your environment? (If it applies)
System:
OS: macOS 13.6
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.11.1 - /private/var/folders/8y/99byt5ms31d1z8jgjfmyvcg80000gn/T/xfs-f1930489/node
Yarn: 3.2.1 - /private/var/folders/8y/99byt5ms31d1z8jgjfmyvcg80000gn/T/xfs-f1930489/yarn
Databases:
SQLite: 3.39.5 - /usr/bin/sqlite3
Browsers:
Chrome: 124.0.6367.62
Safari: 16.6
npmPackages:
@redwoodjs/auth-auth0-setup: 7.4.2 => 7.4.2
@redwoodjs/cli-data-migrate: 7.4.2 => 7.4.2
@redwoodjs/core: 7.4.2 => 7.4.2Are you interested in working on this?
- I'm interested in working on this
Source: redwoodjs/graphql