[master] Progress bar leaves artifacts in output

Bug #321935 reported by Matthew Fuller
70
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
High
Martin Pool

Bug Description

With up to date bzr.dev:

% bzr info http://bazaar-vcs.org/bzr/bzr.dev/
Repository branch (format: pack-0.92)
Location:
  shared repository: http://bazaar-vcs.org/bzr/
  repository branch: http://bazaar-vcs.org/bzr/bzr.dev/
| 1kB @ 0kB/s
Related branches:
    push branch:
  parent branch: http://bazaar-ng.org/bzr/bzr.dev/

Tags: progress

Related branches

Martin Pool (mbp)
Changed in bzr:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Matt Nordhoff (mnordhoff) wrote :

This can happen to any other command as well, of course. "info" is just the easiest one to reproduce.

Revision history for this message
Alexander Belchenko (bialix) wrote :

It's even much worse today:

C:\work\Bazaar\plugins\scmproj\docs\tutorial>bzr info http://bazaar.launchpad.net/~scmproj-dev/bzr-scmproj/tutorial
Standalone branch (format: 1.9 or development-wt5)
Location:B @ 1kB/s
  branch root: http://bazaar.launchpad.net/%7Escmproj-dev/bzr-scmproj/tutorial/
- 10kB @ 1kB/s

summary: - Progress bar leaves artifacts in info output
+ Progress bar leaves artifacts in output
Martin Pool (mbp)
summary: - Progress bar leaves artifacts in output
+ [master] Progress bar leaves artifacts in output
Changed in bzr:
assignee: nobody → Martin Pool (mbp)
importance: Low → High
Revision history for this message
Wouter van Heyst (larstiq) wrote :

Martin, should additional sites of artifacts be filed in a new bug, mentioned here, another approach?

`bzr launchpad-login` is another case where it happens.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 321935] Re: [master] Progress bar leaves artifacts in output

2009/4/30 Wouter van Heyst <email address hidden>:
> Martin, should additional sites of artifacts be filed in a new bug,
> mentioned here, another approach?

Feel free to add them here, but at this point knowing other places
it'll occur is not particularly helpful to fixing the bug. It can
happen at any point where we do output intermixed with transport
activity.

Once I think it's generally fixed hearing about cases where it's not
may be useful.

I'll try to get back to it soon.

--
Martin <http://launchpad.net/~mbp/>

Revision history for this message
Alexandre Garnier (zigarn) wrote :

I have the same problem with a lot of command, but the progress bar stay in the next prompt if there is no response :

$ bzr status
$ ] <bzrlib < 0KB 0KB/s |

And it stay on the first line of output :

$ bzr status
modified: ] <bzrlib < 0KB 0KB/s |
  .bzrignore
$

This problem doesn't appear on all system :
 - problem on RHEL4 with custom install (via --home), bash shell
 - no problem on Ubuntu 9.04 with normal install, bash shell

Is there a way to not show this progress bar ?

Revision history for this message
Martin Pool (mbp) wrote :

Alexandre: from bzr 1.17dev onwards, you can set the environment variable BZR_PROGRESS_BAR=none and they'll be turned off altogether.

Revision history for this message
Martin Pool (mbp) wrote :

Robert suggests that to at least un-regress this bug, we can simply stop showing activity when there's no progress bar. This is not ideal but it's easy and this bug is annoying.

Changed in bzr:
status: Confirmed → In Progress
Revision history for this message
Martin Pool (mbp) wrote :

A fix is merged to trunk for 1.17.

Followon bug 392435, bug 392436.

Changed in bzr:
milestone: none → 1.17
status: In Progress → Fix Released
Revision history for this message
Grant Rettke (grettke) wrote :

The fix is to remove the progress bar?

Revision history for this message
Martin Pool (mbp) wrote :

2009/6/27 Grant Rettke <email address hidden>:
> The fix is to remove the progress bar?

No, the fix is that they're now erased when other output will be sent.

--
Martin <http://launchpad.net/~mbp/>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.