TortoiseBzr doesn't always clean up the bzr locks after an action

[P. van der Velde]

In some cases (mainly seems to happen on commit, pull and merge) a lock remains behind on a branch after TortoiseBzr has finished working. This seems mostly the case when either:
- The TortoiseBzr action fails (e.g. due to a network error or something else)
- The commit window stays open for a long time before starting the commit (e.g. the user is typing a long message)

Unfortunately there is no way to break a lock from TortoiseBzr so you have to drop back to the command line again to fix the problem.

[Gary van der Merwe (garyvdm)]

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

Please could take a look in My Documents\.bzr.log when this happens, and
look at the end of the file for any errors. Having these errors will
help us locate the code that badly structured.

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

iEYEARECAAYFAky2zP4ACgkQd/3EdwGKOh01IACgrVFfDM9A7tsVMbt510TFoarR
OQ4AnRovztr3Uo4qYDXi3J5Ba5g3iu42
=Fbxm
-----END PGP SIGNATURE-----

[P. van der Velde (petrikvandervelde)]

I've finally managed to reproduce this. Todays section of the bzr log is attached. I can't quite remember what the order of all actions was but I do know that I had the commit dialog open while adding more items to the repository (through the add dialog). I then hit refresh in the commit dialog and committed the changes. After that there was a lock that shouldn't have been there.

[P. van der Velde (petrikvandervelde)]

I had another incident like this yesterday where I had the commit dialog open for a considerable amount of time (maybe 20mins) when I got distracted while writing my commit message. After committing the lock was there again.