Closed GoogleCodeExporter closed 8 years ago
I've seen this, too, but it's intermittent AFAIK. Do you have a reproducible
test case?
Original comment by djc.ochtman
on 31 Mar 2010 at 4:31
I have no test case, no. I suspect that it's insufficient handling of EINTR,
which
Python std lib isn't very good at.
Original comment by chadmill
on 31 Mar 2010 at 4:46
I do have Python commit privs as well, so if you can come up with a solution
for that...
Original comment by djc.ochtman
on 31 Mar 2010 at 4:51
I'm using desktop-couch here for gwibber (well, not using, but I'm packaging
it). I
managed to get it to start once / twice, and now always see this error.
Anything I
can provide to track it?
Original comment by dominiqu...@gmail.com
on 10 Apr 2010 at 8:29
Hey, dominique, I hope you can still reproduce this!
The exception handler just above the line referenced in the traceback
'''File "/usr/lib/pymodules/python2.6/httplib2/__init__.py", line 871, in
_conn_request'''
looks interesting to me. Can you find out if you're arriving inside that
exception
handler, and what exception is raised? I don't think it's good to be eating
all
socket.error exceptions that way.
Note, it's inside a retry loop. Maybe the line *after* the exception handler
should
catch this AttributeError also.
I hope to spend some time on this next week.
Original comment by chadmill
on 10 Apr 2010 at 1:43
The current tip catches and retries on ECONNRESET and EPIPE. Do you think we
should
retry on EINTR as well?
Original comment by djc.ochtman
on 10 Apr 2010 at 4:05
This is a known issue in httplib:
http://code.google.com/p/httplib2/issues/detail?id=62
Original comment by thisfred@gmail.com
on 19 Apr 2010 at 10:46
We no longer use httplib2, so I don't think that part applies here.
Original comment by djc.ochtman
on 22 Dec 2010 at 11:59
Okay, this is done.
Original comment by djc.ochtman
on 21 Sep 2012 at 7:20
Original issue reported on code.google.com by
chadmill
on 31 Mar 2010 at 4:25