Replies: 1 comment
-
|
because calling runSync halts all async operations. Which means that the calling process can't read the child stdout and stderr. If the child stdout and stderr are not being read, once the child processes io buffers fill, the child process will hang. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I suddenly wondered how it is done in DCli since waitFor is deprecated. So I traced a little bit and found that the key is the use of Isolate and the blocking call Mailbox.take(). But why? Why not just use Process.runSync()?
Beta Was this translation helpful? Give feedback.
All reactions