-
Notifications
You must be signed in to change notification settings - Fork 3k
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
pyzmq 13.0.0 breaks distribution #58
Comments
Just pushed a fix (ba9ec8c) for this. Thanks for reporting. |
Seems like this has not been released. From what I can tell? Could you push a new version? |
I'll try to push out 0.7 in the upcoming week. Would like to get #83 done, and make sure the documentation reflects all changes. |
Seems this is still released... any updates? |
yeah i have this same issue, should i be using git version of locustio? |
pancaprima
added a commit
to pancaprima/locust
that referenced
this issue
May 14, 2018
* change dependencies order in setup.py (locustio#54) * bugfix when hide edit modal while stopping and edit modal still open (locustio#56) * rizal new feature upload test file to eb (locustio#53) * upload test file to deployed eb * enable user to upload test file to deployed eb reload list on selector after file uploaded writing files to slaves distribute file to slaves and reload the test list route config json to user fileio update directories dinamycally reload after upload, populate directory list modify interface add confirmation dialog * fix non geometric elements * fix test not reloaded when not in master slave mode, css file and alert message * erlangga feature create new json keys (locustio#52) * Revert "erlangga feature create new json keys (locustio#52)" (locustio#57) This reverts commit acccdf5.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just tried to get setup with a distributed swarm today and kept getting this error from zmq:
pyzmq is now more strict about which attributes you can set on a socket. This seems to be caused by a recent zmq update (to version 13.0.0 from 2.2.0.1, 11 days ago). Installing 2.2.0.1 explicitly fixed the problem:
1 derek@DEREKS_MACBOOK_PRO_LOCAL s004 ~/load-testing> pip install pyzmq-2.2.0.1
The text was updated successfully, but these errors were encountered: