Bazaar

  1. Series 2.4
  2. Bug #819604
  3. Comment #1

Comment 1 for bug 819604

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 819604] Re: when an idle ssh transport is interrupted, bzrlib errors

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/2/2011 12:45 PM, Jelmer Vernooij wrote:
> ** Changed in: bzr Importance: High => Critical
>
> ** Changed in: bzr Assignee: (unassigned) => canonical-bazaar
> (canonical-bazaar)
>

Is this actually critical?

Also, the initial report was "idle ssh transport". Monty's traceback is
certainly not 'idle' given that we are actively fetching content.

And while the transfer-of-content is roughly stateless, I'm not 100%
sure we want to default-reconnect SSH connections.

I suppose we could use a reasonable try-again-but-not-forever, or
try-once-but-fail-if-last-connect-failed. People with flaky connections
would get slow-but-useful connections. Restarting codehosting would
allow things to continue roughly interrupted, but the network going down
wouldn't cause us to spin indefinitely.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk48AXUACgkQJdeBCYSNAANUhQCgqCGM8zIhGfqife6E2TIaLwQx
Nc4AnRq18lIiBiyGM6t7/uy+SmXgQlXt
=8wVS
-----END PGP SIGNATURE-----