| 2008-09-23 02:21:45 |
Andrew Bennetts |
bzr: statusexplanation |
|
Thanks for the report. I see the cause: yet another situation where a finally block tramples the original exception. This time it's the finally clause in BzrBranch.push. It shouldn't be hard to fix.
bzr sitting idle for 40 minutes is just normal TCP behaviour; the client has sent a request to the server and is waiting for a response, and if the connection goes away while waiting for the response then most TCP implementatons won't notice for a very long time. My initial feeling is that it's not worth trying to do something about this (e.g. add a no-op request and the ability to send them while a real request is outstanding so that the client can periodically send pings that would cause stale TCP connections to expire sooner). Feel free to open a separate bug report for that issue if it would be useful to you, though. |
|
