On 18 February 2014 18:50, Roberto De Ioris <[email protected]> wrote: > >> Since I did a bit of digging into this I thought I'd sent a short >> message about it to the list since there wasn't anything equally >> informative online when I searched. >> >> When upgrading to 1.9.20 to 2.0 we started getting "error while >> streaming PSGI response" errors on various live requests when calling >> $writer->write($part) when using the streaming PSGI API. >> >> It turned out that this was happening all along before 2.0, but was >> just being silently ignored, this is the relevant commit that first >> appeared in 1.9.21: https://github.com/unbit/uwsgi/commit/46cceb0 >> >> This happens when a client aborts a request on their side, I solved it >> just by wrapping the ->write() call in an eval and logging when this >> happens. > > Is wrapping it a good solution ? > > That croak is there otherwise the server could never knows about client > being disconnected. > > How do you manage it ? > > This is an interesting (language-independent) problem, that i would like > to better address
When Aevar showed me the code my first thought was that it should have been a warning. In Perl there are internal API's for checking if warnings are enabled, which IMO would put control in the right place. Yves -- perl -Mre=debug -e "/just|another|perl|hacker/" _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
