Hang at commit time when using sftp or bzr+ssh

[Stephen AuYeung]

We have a long running process that will perform all bzr operations. I believe that the lock will not be held across operations.

Will there be cached objects, e.g., the master branch object, that can safely stay across locks?

Thanks,
Stephen

-----Original Message-----
From: Aaron Bentley [mailto:aaron at aaronbentley.com] 
Sent: Friday, December 09, 2011 7:28 AM
To: stephen at ck12.org
Cc: 'Martin Packman'; bazaar at lists.canonical.com
Subject: Re: Hang at commit time when using sftp or bzr+ssh

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

On 11-12-08 07:23 PM, Stephen Auyeung wrote:
> Another possibility is caching at the higher level. For example, 
> caching the master_branch at Branch. I see the code there, but the 
> cache is being cleared when unlock is called and that makes the cache 
> not very useful. Could it be that only some of the cache need to be 
> clear but not all?

Generally the solution is to hold the lock for longer.  Is there a reason that wouldn't work here?

I think we want to avoid the possibility of inconsistency clearing only part of the cache would introduce.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7iKOkACgkQ0F+nu1YWqI14JACeIAAlH8GwPyNgwKBLnOoeMopD
QwsAn1n2dGabEEXeM2CyyYRFsHqdNP9z
=yRsf
-----END PGP SIGNATURE-----