You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting Gunicorn with aiohttp worker(s), if the app uses subprocess to start other processes and captures the output, their returncode is in most cases 0, even if the actual exit code was 1.
The PR to fix the issue is by the same person who opened the issue, so they clearly considered it fixed. Feel free to open a new issue with details of what your seeing (creating a PR with a test reproducing the problem would be best).
Describe the bug
When starting Gunicorn with aiohttp worker(s), if the app uses
subprocess
to start other processes and captures the output, theirreturncode
is in most cases0
, even if the actual exit code was1
.To Reproduce
Then run it with:
Expected behavior
The detected
returncode
should always be1
, as the subprocess always exits with1
.Logs/tracebacks
Python Version
aiohttp Version
multidict Version
yarl Version
OS
macOS Big Sur 11.5.2 (20G95)
Related component
Server, Client
Additional context
You can refer to the same question
encode/uvicorn#894
encode/uvicorn#895
I guess bug in https://github.com/aio-libs/aiohttp/blob/master/aiohttp/worker.py
Code of Conduct
The text was updated successfully, but these errors were encountered: