On Monday, December 18, 2017 at 3:00:23 PM UTC+1, Christian Schafmeister wrote: > > I fixed the problem last night - it turned out to be a threading issue. > When I rapidly evaluated notebook cells (hitting shift-enter really fast) > the Python in Jupyter Notebook would crash as shown. > Multiple processes were calling the pzmq:send function at the same time > and the messages were becoming interleaved and garbled. > I wrapped a mutex around the function that calls pzmq:send multiple times > and the problem went away. >
That sounds like a serious bug. Jupyter is supposed to handle simultaneous requests from multiple clients to the same kernel, afaik. This should not garble messages. Are you sure that the problem is on the sending side? Or could it be that your kernel expects messages in sequence, although the messaging protocol makes no guarantees about that? It's not impossible that you found a problem in Jupyter. But it seems strange that something so fundamental would have gone unnoticed until now. If you think that problem is in Jupyter, please open an issue and point us to the code where you had to implement the fix. best regards, Roland -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/34f04b0e-8a6b-42f4-8f0e-754f4d9d66c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
