-
Notifications
You must be signed in to change notification settings - Fork 4
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
review feedback #1
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/cc @trentm
"Somewhere"?
You need to be diligent
It seems a bit unclear. I get what you mean but that's because we talked about
it face to face.
Does the "most likely" refers to the fact that it relies on libuv's
implementation details, and so that if (among other things) either:
the order with which libuv's event loop processes I/o and setImmediate
changes
there are more than the limit of file descriptors for which events can be
process in a single turn of the loop
are true, things might not work?
Actually, you're covering that later in the document, nevermind.
That's assuming nothing is scheduled to run on the event loop when
exeunt
iscalled. If there are still active handles, it's not the case.
Yes: nodejs/node@ab3306a
There are a lot (at least 10) of issues in nodejs/node related to this. One that
was aimed at tracking most of them was
nodejs/node#6980. However, some issues falling into
that topic were not equivalent. For instance, some were about TTYs only and
others were about pipes only.
The text was updated successfully, but these errors were encountered: