Paul J. Dorn

Updated version, with commits split for different cleanup: https://github.com/benoitc/gunicorn/compare/master...pajod:gunicorn:patch-py36 No harm in merge conflicts, can always be trivially regenerated thanks to https://pypi.org/project/pyupgrade/

Its merged as https://github.com/benoitc/gunicorn/commit/f0c91cca484820d1034f3a5278c0662aed2a23ea (the difference being the exception has a name now) so this PR is no longer needed. I still do not like how its *handled* though, but...

Expression of policy: Consider "At this time.." => "Please target reports against :white_check_mark: or current master. Please understand that :x: will not receive further security attention." and "latest release" =>...

@marcomilone this might be a good test case to validate some outstanding patches in that area against. Please go ahead and share a full reproducer, or at least a full...

@ashasanm Only `--log-level debug` gives you the error (PR #3191 is one suggestion how making this easier to figure out). You probably did not want to create a Win32 (C:)...

What does `gunicorn --version` say? What is the command that you configured supervisord to launch? I wonder if you have hit a problem in an unreleased version (127 is typically...

Even if you cannot provide a full reproducer, please do add more details: `--print_config` and the call / type of object that is used/shared by the sub-threads? If it is...

Unable to trigger it like that on Python 3.11.2 / gevent 23.9.1 / greenlet 3.0.2 / flask 3.0.0 - it will always give me a nice traceback on unhandled exceptions...

What scenario would this be useful in (or even observably different from defaults)? Are you concerned about the **2 hour** timeframe, which I fear may not be easy to write...

What exactly do you want to solve? Why are you setting max_requests in the first place? (You should not generally be using the autorestart feature, it merely assists in mitigating...