Hi Julian, On Sun, Mar 20, 2016 at 12:27 PM, Julian Taylor <jtaylor.deb...@googlemail.com> wrote: > On 20.03.2016 11:11, László Böszörményi (GCS) wrote: >> Sorry, my life was chaotic. Yes and no, checked it. First, there's a >> new upstream version of pyzmq (15.2) for two months. It seems to be >> security related according to the release log[1]: >> - FIX: unicode/bytes bug in password prompt in zmq.ssh on Python 3 >> - workaround overflow bug in libzmq preventing receiving messages >> larger than MAX_INT [...] > The latest version does unfortunately not fix the problem. It is also > not security related, it just could not send large data due to bugs in zmq. > I guess a good approach would be to bisect zmq to see what they changed > to cause it. Just a friendly ping; could you test the latest Git master if that fixes the hang and/or could you ask upstream for advice? Should I do it? It seems it constantly get fixes that may be relevant.
Cheers, Laszlo/GCS
