Branch isn't unlocked on error
Bug #447302 reported by
Levi Bard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-rewrite |
Fix Released
|
Low
|
Jelmer Vernooij |
Bug Description
If an error occurs during a rebase operation, the branch isn't unlocked, and it's necessary to break-lock in order to proceed.
Steps to reproduce:
* Unplug network cable.
* Attempt to rebase from remote branch.
* Wait for timeout exception.
* Replug network cable.
* Attempt to rebase from remote branch.
Expected result: Rebase will work (or fail normally)
Actual result: Branch is locked, break-lock is necessary.
This happened while rebasing from a svn repo to an unbound branch on win32, bzr 2.0.0, bzr-rebase 0.5.3.
Changed in bzr-rewrite: | |
status: | Incomplete → Triaged |
importance: | Undecided → Low |
status: | Triaged → Fix Committed |
assignee: | nobody → Jelmer Vernooij (jelmer) |
milestone: | none → 0.6.1 |
Changed in bzr-rewrite: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I can't reproduce this, please provide a backtrace of the original timeout exception (you should be able to find it in ~/.bzr.log) so we can find the place where the unlock is missing.