Hi,

I'm not so convinced anymore that this is a searx issue, because I can
reproduce the problem with uwsgi even with a very simple hello world
application. I filed the details in #900174. As you can see there, it might not
even be a uwsgi problem, because the upgrade of unrelated packages causes this
change in uwsgi...

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to