And use the flask development WSGI server for the response listener in the controller. We are anyway misusing gunicorn right now, and it's causing all sorts of trouble because it catches signals, stop slowly, etc. We should make sure the response listener is works well, and probably that involves using something a bit more robust that the development server in the future, but for now, we'll ditch gunicorn.
And use the flask development WSGI server for the response listener in the controller. We are anyway misusing gunicorn right now, and it's causing all sorts of trouble because it catches signals, stop slowly, etc. We should make sure the response listener is works well, and probably that involves using something a bit more robust that the development server in the future, but for now, we'll ditch gunicorn.