{"action":"created","issue":{"url":"https://api.github.com/repos/celery/celery/issues/3340","repository_url":"https://api.github.com/repos/celery/celery","labels_url":"https://api.github.com/repos/celery/celery/issues/3340/labels{/name}","comments_url":"https://api.github.com/repos/celery/celery/issues/3340/comments","events_url":"https://api.github.com/repos/celery/celery/issues/3340/events","html_url":"https://github.com/celery/celery/issues/3340","id":167454399,"number":3340,"title":"Celery tasks are again not allowed to start subprocesses","user":{"login":"lvh","id":97816,"avatar_url":"https://avatars.githubusercontent.com/u/97816?v=3","gravatar_id":"","url":"https://api.github.com/users/lvh","html_url":"https://github.com/lvh","followers_url":"https://api.github.com/users/lvh/followers","following_url":"https://api.github.com/users/lvh/following{/other_user}","gists_url":"https://api.github.com/users/lvh/gists{/gist_id}","starred_url":"https://api.github.com/users/lvh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lvh/subscriptions","organizations_url":"https://api.github.com/users/lvh/orgs","repos_url":"https://api.github.com/users/lvh/repos","events_url":"https://api.github.com/users/lvh/events{/privacy}","received_events_url":"https://api.github.com/users/lvh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-25T20:11:54Z","updated_at":"2016-07-25T20:21:20Z","closed_at":null,"body":"This is a regression of #1709. It looks like this causes issues like https://github.com/ansible/ansible/issues/14408 in addition to the ones mentioned in #1709.\r\n\r\nThat issue was closed in commit https://github.com/celery/billiard/commit/e6bb0f744e97bd9acc560788a1b6152bc9ba48c3 but then got reintroduced in commit https://github.com/celery/billiard/commit/c7eedbd0ee1498e76d4fa1affac5b1a275660ee7#diff-bf0b236b25b18d8affbc71f0052f9ebfR121. \r\n\r\nI am creating a new issue because I'm trying to fix it, #1709 was closed without being resolved, and I'm not a contributor so I can't reopen it.\r\n"},"comment":{"url":"https://api.github.com/repos/celery/celery/issues/comments/235072327","html_url":"https://github.com/celery/celery/issues/3340#issuecomment-235072327","issue_url":"https://api.github.com/repos/celery/celery/issues/3340","id":235072327,"user":{"login":"lvh","id":97816,"avatar_url":"https://avatars.githubusercontent.com/u/97816?v=3","gravatar_id":"","url":"https://api.github.com/users/lvh","html_url":"https://github.com/lvh","followers_url":"https://api.github.com/users/lvh/followers","following_url":"https://api.github.com/users/lvh/following{/other_user}","gists_url":"https://api.github.com/users/lvh/gists{/gist_id}","starred_url":"https://api.github.com/users/lvh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lvh/subscriptions","organizations_url":"https://api.github.com/users/lvh/orgs","repos_url":"https://api.github.com/users/lvh/repos","events_url":"https://api.github.com/users/lvh/events{/privacy}","received_events_url":"https://api.github.com/users/lvh/received_events","type":"User","site_admin":false},"created_at":"2016-07-25T20:21:20Z","updated_at":"2016-07-25T20:21:20Z","body":"The linked PR reverts it back to the old behavior. Of course, as long as the parent (in this case, a celery worker process) doesn't start reaping these, you'll end up with a ton of zombies. My estimation from #1709 is that @ask feels that's better than just arbitrarily not allowing it. We can also introduce behavior for celery to take over that job."}}
{"actor":{"display_login":"lvh"}}