-
Notifications
You must be signed in to change notification settings - Fork 386
LostRemote exceptions while using gevent.zeorpc #62
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
Comments
Hello, Instead of: Try: best, |
Ok, so if I run your test long enough, I get the interrupted syscall exception. Either on the sender or the receiver part of the events object. I am pushing a fix soon. |
Running with 0.4.2, although it passes, it prints alot to stdout:
and the prints to stderr continue until the test finishes running. |
Still fails:
|
there's no re-open button, should I create a new issue? |
I cannot reproduce your problem with: It spans a new sleep 1 every second, and adding print statements shows that the zerorpc service is working fine. I get this message: /!\ gevent_zeromq BUG /!\ catching up after missing event (SEND) /! |
ah after 15min I got one: Traceback (most recent call last): |
I'm using: on which OS are you running on? |
for some reason, zmq thorw EINTR on getsockopt calls now... ref #62
linux. to be accurate I use gevent: git://github.com/surfly/gevent.git@454a77ca561868854760b2d9cbfa3bf3bbd2e062#egg=gevent-dev I just pushed a change on master, try with that... seriously, zmq is now throwing EINTR at every possible call... |
that's gevent-1.0rc2 On Monday, June 10, 2013 at 9:47 AM, François-Xavier Bourlet wrote:
|
now, which your latest change, the test finally passes |
i'll have it running a few more times to be sure. |
as soon as you confirm that it works for you |
seems to be working, passed 3/3. |
done. |
We've been experiencing issues with zerorpc and gevent.subprocess.
Consider the following test:
Running this on CentOS 6.4 fails with:
with gevent-1.0rc2 and zerorpc-0.4.1
The text was updated successfully, but these errors were encountered: