Ctrl-C'ing a push operation == pain
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Martin Pool |
Bug Description
I was bzr push'ing up a branch. It had taken about 30 minutes and wasn't seeming to do much, so I hit Ctrl-C with the intent to restart the push and see if things turned out better. When I Ctrl-C'd, I got the following output:
Exception exceptions.OSError: <exceptions.OSError instance at 0x30e07e90> in <bound method SFTPFile.__del__ of <paramiko.SFTPFile object at 0x30eb7950>> ignored
bzr: ERROR: exceptions.OSError: [Errno 32] Broken pipe
at /usr/lib/
in send
/usr/lib/
warn("branch %r was not explicitly unlocked" % self)
Exception exceptions.OSError: <exceptions.OSError instance at 0x31b71760> in <bound method BzrBranch.__del__ of BzrBranch('sftp://
I imagine this output to be quite difficult to read for someone who isn't a Python programmer (or even for somebody who is a Python programmer, but is much more interested in debugging their own error messages, rather than someone else's. :)
I would have preferred some simple output, like:
push operation cancelled.
When I tried the push again, I got this output:
bzr: WARNING: Unable to update the working tree of: sftp://
bzr: ERROR: bzrlib.
at /usr/lib/
in __init__
I would have expected instead for the push to have resumed where it left off.
Changed in bzr: | |
status: | Fix Committed → Fix Released |
Changed in bzr: | |
status: | In Progress → Fix Committed |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
Fix committed to bzr.dev yesterday, It will be in the 0.82rc2 beta.