Delayed Response + reconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ibid |
New
|
Wishlist
|
Unassigned |
Bug Description
My guess is that this was something that took a while (like coffee / a socket request off campus) and only returned after a TCP timeout had taken the source down. We should handle this gracefully
2009-05-17 13:14:20,691 ERROR twisted: Unhandled exception
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
context.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
--- <exception caught here> ---
File "/usr/lib/
result = f(*args, **kwargs)
File "/home/
source = response[
exceptions.
Hmm, misdiagnosed I think. Any other thoughts?