FS#45316 - [zeromq] upgrade to version 4.0.6-1 breaks ipython support in Spyder IDE
Attached to Project:
Community Packages
Opened by Narunas K. (narunas) - Saturday, 13 June 2015, 16:24 GMT
Last edited by Kyle Keen (keenerd) - Monday, 15 June 2015, 20:04 GMT
Opened by Narunas K. (narunas) - Saturday, 13 June 2015, 16:24 GMT
Last edited by Kyle Keen (keenerd) - Monday, 15 June 2015, 20:04 GMT
|
Details
Description:
Recent upgrade of zeromq to version 4.0.6-1 x86_64 breaks ipython support in Spyder IDE. Additional info: - Name : spyder - Version : 2.3.4-1 - Architecture : any Steps to reproduce: - Upgrade zeromq to version 4.0.6-1 x86_64 (or above?) - Launch Spyder IDE. - Open Ipython console. - Within ~5 sec you will be welcomed by: "It seems the kernel died unexpectedly. Use 'Restart kernel' to continue using this console." View original bug report: https://github.com/spyder-ide/spyder/issues/2485 |
This task depends upon
Closed by Kyle Keen (keenerd)
Monday, 15 June 2015, 20:04 GMT
Reason for closing: Fixed
Additional comments about closing: zeromq-4.1.2-1
Monday, 15 June 2015, 20:04 GMT
Reason for closing: Fixed
Additional comments about closing: zeromq-4.1.2-1
Downgrading to 4.0.5-1 does the magic.
For me downgrading zeromq to 4.0.5 and python2-pyzmq to 14.6.0-1 makes salt-zmq work again (python2-pyzmq 14.6.0-2 with zeromq 4.0.5 does not work due to certain symbols not being available in Python in that constellation).
Just to double check, I have run full system upgrade, which currently for me suggests just two packages:
# pacman -Syu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (2) python2-pyzmq-14.6.0-2 zeromq-4.1.1-1
Total Installed Size: 3.15 MiB
Net Upgrade Size: -0.53 MiB
<...>
# pacman -Q spyder
spyder 2.3.4-1
Now just follow the "Steps to reproduce" and I get this image (attached).
I'm not trying to be difficult, but your patch simply doesn't work for Spyder IDE, it perhaps work for other apps.
Thanks
Yesterday I ran a full system upgrade (pacman -Syu). Then I checked for new configuration files with »pacdiff«; nothing related to zeromq or salt. This was followed by a reboot.
Starting immediately after the reboot my salt-minion went into a restart loop with the aforementioned error message »invalid argument«; see my entries in salt's bug report that I've linked to above.
During that upgrade the following packages were upgraded according to /var/log/pacman.log:
[2015-06-13 22:01] [ALPM] upgraded zeromq (4.0.5-1 -> 4.1.1-1)
[2015-06-13 22:01] [ALPM] upgraded python2-pyzmq (14.6.0-1 -> 14.6.0-2)
[2015-06-13 22:02] [ALPM] upgraded salt-zmq (2015.5.1-1 -> 2015.5.2-2)
First I thought this was due to salt-zmq. I downgraded salt-zmq back o 2015.5.1-1, but no dice, same restart loop in the minion.
Next I downgraded zeromq to 4.0.5-1. No dice either, this time due to missing symbols in Python.
Last I downgraded python2-pyzmq to 14.6.0-1. Right after doing this salt-minion was running normally again.
Next I upgraded salt-zmq to 2015.5.2-2 again. salt-minion is still running normally.
In summary: salt-zmq (both 2015.5.1-1 and 2015.5.2-2) works well with zeromq 4.0.5-1/pythong2-pyzmq 14.6.0-1. Neither version of salt-zmq works with zeromq 4.1.1-1/python2-pyzmq 14.6.0-2.
So please tell me what I've done wrong here…
Maybe this is an issue that only happens with certain configurations. I'm running salt solely via IPv6, if that matters.
Similar for Salt. I looked at issue 24477, saw that ping didn't work, and fixed it so ping worked. If something still doesn't work, I need you to provide a self-contained minimal test case. (Or a patch to fix it.)
https://groups.google.com/forum/#!topic/jupyter/UM-ShiI_Mrs
Quote:
Patches have been accepted to various zeromq branches, so this problem should not affect libzmq-4.0.7 or libzmq-4.1.2, once they are released. I would still recommend kernel authors make the changes proposed above, even though they will not be necessary after the next patch release of libzmq.
It seems that zeromq v4.1.1 has this exact same bug, which will be resolved in the upcoming releases.