-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
Deadlock when running commands that spawn background processes #310
Comments
Thanks for reporting @flupke, I will look into it |
I hit this issue as well. A dirty workaround is to call something like |
provide a "force done" event that causes the output threads to stop attempting to read from stdout/stderr in the cases where they would never finish. closes #310
So after some investigation, the way I see it is:
We could add an option saying "hey, I know this process will launch a subprocess and cause stdout/stderr to never finish, so disable reading on them." but that seems like it requires too much knowledge of what the process does under the hood, and will probably result in a lot of people creating issues, wondering about hanging, and then people try to debug it. I've opted for a hacky approach (here and here) that requires no knowledge of the process. What it does is, when the process ends, we say "ok, threads that are spinning and trying to read from stdout and stderr, you have X seconds to finish reading from those streams, then you're done." Most processes stdout/err will receive their EOFs immediately, so the timer behavior won't apply to them. The timer behavior will only kick in on processes that have dup'd their fds in another child process, and will therefore never EOF. In that case, the process will hang for half a second on completion, but then terminate correctly the fix is on the |
Cool! I tested the branch against my script above, and it doesn't hang anymore. There are error messages though:
|
@flupke Weird, works fine for me, but I went ahead and reverted the lines that are causing the errors. Want to give it another try? |
Yup, all good! (this was on mac btw) On Fri, Oct 7, 2016 at 9:07 PM Andrew Moffat notifications@github.com
|
* added `_out` and `_out_bufsize` validator [#346](amoffat/sh#346) * bugfix for internal stdout thread running when it shouldn't [#346](amoffat/sh#346) * regression bugfix on timeout [#344](amoffat/sh#344) * regression bugfix on `_ok_code=None` * further improvements on cpu usage * regression in cpu usage [#339](amoffat/sh#339) * fd leak regression and fix for flawed fd leak detection test [#337](amoffat/sh#337) * support for `io.StringIO` in python2 * added support for using raw file descriptors for `_in`, `_out`, and `_err` * removed `.close()`ing `_out` handler if FIFO detected * composed commands no longer propagate `_bg` * better support for using `sys.stdin` and `sys.stdout` for `_in` and `_out` * bugfix where `which()` would not stop searching at the first valid executable found in PATH * added `_long_prefix` for programs whose long arguments start with something other than `--` [#278](amoffat/sh#278) * added `_log_msg` for advanced configuration of log message [#311](amoffat/sh#311) * added `sh.contrib.sudo` * added `_arg_preprocess` for advanced command wrapping * alter callable `_in` arguments to signify completion with falsy chunk * bugfix where pipes passed into `_out` or `_err` were not flushed on process end [#252](amoffat/sh#252) * deprecated `with sh.args(**kwargs)` in favor of `sh2 = sh(**kwargs)` * made `sh.pushd` thread safe * added `.kill_group()` and `.signal_group()` methods for better process control [#237](amoffat/sh#237) * added `new_session` special keyword argument for controlling spawned process session [#266](amoffat/sh#266) * bugfix better handling for EINTR on system calls [#292](amoffat/sh#292) * bugfix where with-contexts were not threadsafe [#247](amoffat/sh#195) * `_uid` new special keyword param for specifying the user id of the process [#133](amoffat/sh#133) * bugfix where exceptions were swallowed by processes that weren't waited on [#309](amoffat/sh#309) * bugfix where processes that dupd their stdout/stderr to a long running child process would cause sh to hang [#310](amoffat/sh#310) * improved logging output [#323](amoffat/sh#323) * bugfix for python3+ where binary data was passed into a process's stdin [#325](amoffat/sh#325) * Introduced execution contexts which allow baking of common special keyword arguments into all commands [#269](amoffat/sh#269) * `Command` and `which` now can take an optional `paths` parameter which specifies the search paths [#226](amoffat/sh#226) * `_preexec_fn` option for executing a function after the child process forks but before it execs [#260](amoffat/sh#260) * `_fg` reintroduced, with limited functionality. hurrah! [#92](amoffat/sh#92) * bugfix where a command would block if passed a fd for stdin that wasn't yet ready to read [#253](amoffat/sh#253) * `_long_sep` can now take `None` which splits the long form arguments into individual arguments [#258](amoffat/sh#258) * making `_piped` perform "direct" piping by default (linking fds together). this fixes memory problems [#270](amoffat/sh#270) * bugfix where calling `next()` on an iterable process that has raised `StopIteration`, hangs [#273](amoffat/sh#273) * `sh.cd` called with no arguments no changes into the user's home directory, like native `cd` [#275](amoffat/sh#275) * `sh.glob` removed entirely. the rationale is correctness over hand-holding. [#279](amoffat/sh#279) * added `_truncate_exc`, defaulting to `True`, which tells our exceptions to truncate output. * bugfix for exceptions whose messages contained unicode * `_done` callback no longer assumes you want your command put in the background. * `_done` callback is now called asynchronously in a separate thread. * `_done` callback is called regardless of exception, which is necessary in order to release held resources, for example a process pool
The issue is described in details here: http://bugs.python.org/issue4216#msg77582
The issue is visible for example with git over ssh, when using ssh's
ControlMaster
option. Basically, it hangs because sh waits to receive an EOF on git's stream, which never happens because ssh inherited git's streams and survives past git's end.Here's how to reproduce with sh:
You also need to enable persistent ssh connections in your
~/.ssh/config
:I think there should be an option to completely disable sh reading on streams (
_no_out
and_no_err
don't help, neither does redirecting streams to files).The text was updated successfully, but these errors were encountered: