Bazaar

  1. Bug #592148
  2. Comment #1

Comment 1 for bug 592148

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 592148] [NEW] timeout for LockContention retry is always 0 for smart server

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

Parth Malwankar wrote:
> Public bug reported:
>
> The timeout for LockContention retry is always 0 for smart server. Due to this, the retry does not happen.
> I put some checks in bzrlib.lockdir.wait_lock.
> if timeout is None:
> timeout = _DEFAULT_TIMEOUT_SECONDS
> While lockdir.py initialized _DEFAULT_TIMEOUT_SECONDS to 300, the actual value at runtime is 0.
>
> I am using trunk (2.2b3) on Lucid.
>

This is actually by design. The problem is that it was hanging on the
server side, without having the user know what they could do.

If you look closely, the default is overridden inside 'cmd_serve'.

 status: wontfix

John
=:->

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

iEYEARECAAYFAkwQ9VoACgkQJdeBCYSNAAP5UQCg1Lz7/BR8p01UqXUs1bLMjk7H
EioAn3HwMscsPL49RnNkwCuNtfO/2S4L
=WT3D
-----END PGP SIGNATURE-----