New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"ZMQError: Interrupted system call" when saving inline figure #499
Comments
Confirmed. Note that because the ZMQ threads are dead, we can no longer communicate with the kernel after that. I'm going to set this as critical for now because of that - tagging @minrk, @ellisonbg |
I just submitted another issue, #500, which might be related (?) |
Possibly, but at a glance, it looks unrelated. |
I can reproduce this on Linux, but not on OSX. As far as I can tell, the QtGui.QFileDialog constructor sends a spurious SIGINT to all child threads, which is completely stupid and bizarre, but I guess we have to deal with it. There is an issue in pyzmq where EINTR used to produce a warning and continue the loop, but now (as of 2.0.8) will raise. This will be fixed in 2.1.8 (or 2.1.7.2), but I don't think we can depend on that. |
I forgot to mention, I'm on Ubuntu 10.10 x86-64 with zmq and pyzmq 2.1.7. |
Should be fixed by #501, can you test? |
Yup, that seemed to do it. Thanks! By the way, what's the typical way to apply a single commit like this from github to your local branch? I tried stuff like
as well as |
Cherry pick requires the commit to be in your local content. So: git remote add minrk https://github.com/minrk/ipython.git git fetch minrk then On Jun 2, 2011, at 18:42, mspacekreply@reply.github.com wrote:
|
Thanks minrk. I'm coming from bzr. Hopefully I'll get the hang of git eventually. |
closes ipythongh-499 closes ipythongh-501
Running
ipython-qtconsole --pylab=inline
, and thenplot(range(10))
, followed by right clicking on the inline figure and choosing either "Save Image As..." or "Save SVG As... " generates:The file save dialog box does come up though, and the image saves correctly.
The text was updated successfully, but these errors were encountered: