-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add a catch to nativeStream.write(..) to avoid server crash. #7758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 7f5fc29 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @itsthesteve for your help
It looks great to me.
@wmertens thoughts?
Hey I think I see I still have issues here there are many more .write(..) places I'll try to think of a better approach. |
On second thought, I may be over my head here. Let me know what you think we should do here @gioboa @wmertens
|
What is it?
Description
There is an edge case as part of ssr rendering, where the server gotten an error after the headers are sent, the async nature of write(..) could trigger an error and if uncaught the process crashes.
Checklist
pnpm change