{"push_id":2488651997,"size":1,"distinct_size":1,"ref":"refs/heads/fix-async-exitcode","head":"28a227c843020ced796ebbfb550c302b07dafc20","before":"52ea0eac1f5495077dd4b2c466a275af2bb4a54f","commits":[{"sha":"28a227c843020ced796ebbfb550c302b07dafc20","author":{"name":"Matthijs Kooijman","email":"9dc3ff3d138562f97538d2d6494f1e5dc216015b@stdin.nl"},"message":"fix exit code when running under asio\n\nWhen using a boost::asio::io_context, `io_context_ref` is expected to\nhandle SIGCHLD, call waitpid and store the exit code of the process. In\naddition to storing the exit code, it also handles calling\n`on_exit_handler` on any `async_handler` instances (e.g. when using\n`on_exit`).\n\nHowever, there was a check that only set up the SIGCHLD handling when\nthere were any `async_handler` instances present. So when there are none\n(which is usually the case), the exit code is also not set, resulting in\nan invalid result when calling `exit_code()`. To fix this, the check is\nsimply removed, so now a SIGCHLD handler is always set up when an\n`io_context` is passed.\n\nThis check was introduced in commit 7017150 (added specialization for\nposix && added conditional for io_service_ref).","distinct":true,"url":"https://api.github.com/repos/matthijskooijman/boost-process/commits/28a227c843020ced796ebbfb550c302b07dafc20"}]}
{"actor":{"display_login":"matthijskooijman"}}