bzr doesn't gracefully handle interrupted push/branch operations
Bug #45504 reported by
John Dong
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
John A Meinel | ||
Bug Description
If a keyboard interrupt, network/system failure, or any other event interrupts a branch or push operation, bzr is unable to resume or even gracefully re-initiate the previous operation. Instead, cryptic errors are presented to the user (no WorkingTree for interrupted branch, File Exists for push). Users have to remove .bzr by hand for bzr to function properly again.
This is terribly confusing to the novice user and annoying to the experienced user. Bzr should either
(a) Gracefully recover from interrupted actions, either by resuming from where it left off (preferable) or even cleaning out its previous attempt and starting from scratch
or (b) Recognize this situation and ask the user in an understandable message to remove .bzr
Revision history for this message
| David Allouche (ddaa) wrote | #1 |
Revision history for this message
| David Allouche (ddaa) wrote | #2 |
Revision history for this message
| David Allouche (ddaa) wrote | #3 |
Revision history for this message
| John A Meinel (jameinel) wrote | #4 |
| Changed in bzr: | |
| assignee: | nobody → jameinel |
| status: | Unconfirmed → In Progress |
| status: | In Progress → Fix Committed |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 45504] Re: bzr doesn't gracefully handle interrupted push/branch operations | #5 |
| Changed in bzr: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is that a duplicate of bugj 53340?