Comment 6 for bug 537116

Wondering if there's any progress on the one hour timeout issue? I just tried bzr branch with web2py again, and it hung and then timed out an hour later, just as in this report.

Note this branch is into an empty directory. Here's where it stopped:
$ bzr branch --use-existing-dir lp:~mdipierro/web2py/devel web2py
- 104344KB 30KB/s | Fetching revisions:Inserting stream

And an hour later:
FATAL ERROR: Server unexpectedly closed network connection
bzr: ERROR: Connection closed: Unexpected end of message. Please check connectiv
ity and permissions, and report a bug if problems persist.

IIRC the conclusion before was that there was a very large revision, and a lot of behind the scenes activity, but not what launchpad monitors to determine if the connection is idle. In the original case, the existence of a large revision was confirmed, and the same hang and timeout was reproduced on a single revision, by doing a bzr branch to rev 1, then bzr pull to extract individual revsions, one at a time.

My network connection is DSL but not a really expensive high-speed line. The last time I needed to branch web2py, the "workaround" was to find someone with a very high-speed connection who did the branch, tarred up the result and sent it to me.

Proposed solution was to have lp monitor both ports (or however the activity is partitioned). Proposed temporary workaround was to increase the "idle" timeout.