Before anyone spends too much time reproducing this in other languages, I have identified it something Python specific.
Summary: the device subprocess is getting torn down forcefully by garbage collection at the end of the script, which is what caused message loss. Any method of preventing that (e.g. not trying to exit until the device has done what it is supposed to, setting Process.daemon=True, etc.). Further explanation on GitHub<https://github.com/zeromq/pyzmq/issues/149#issuecomment-2484547> . On Fri, Oct 21, 2011 at 11:09, James Thornton <[email protected]>wrote: > On Fri, Oct 21, 2011 at 8:06 AM, Chuck Remes <[email protected]> > wrote: > > > > I don't have a python environment set up, so reproducing this exactly > isn't feasible for me. > > I may rewrite it in Ruby and see what happens. > > No problem. I reproduced it on Ubuntu under ZMQ 1.2.11 and the latest > pyzmq -- filed an issue here > (https://github.com/zeromq/pyzmq/issues/149). > > - James > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
