| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
If a socket is sent to a child, any data that is buffered in the socket will not be sent to the child. The child will only receive data from the socket that is sent after the child has the socket.
|
To be clear, this is a backport from master. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Also, I think we're still using v4.x-staging for backporting commits instead of v4.x directly. |
Sorry, something went wrong.
|
we indeed use v4.x-staging. Generally we also maintain the original meta data... so you should include PR-URL: #6951 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> at the end of the commit message regarding staging, I'll make sure to land it to that branch, no need to open another PR |
Sorry, something went wrong.
|
Manually landed with appropriate meta data in cf43254 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
doc/child_process
Description of change
If a socket is sent to a child, any data that is buffered in the
socket will not be sent to the child. The child will only receive
data from the socket that is sent after the child has the socket.
PoC:
From #6951: