[Bug 4248] New: Messages from mercurial server are not displayed during a push until unbundle ends

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=4248

          Priority: normal
            Bug ID: 4248
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Messages from mercurial server are not displayed
                    during a push until unbundle ends
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: mh+hg at glandium.org
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.9.2
         Component: Mercurial
           Product: Mercurial

The typical scenario where this ends up being a problem is the following:
- Someone pushes to $repo on $server, and for some reason, the push takes a
long while.
- Someone else pushes to $repo on $server.
- The server emits a "waiting for lock on repository /path/to/repo held by
'$server:$pid'" message, but it's not visible to the user
- First person's push ends
- Second person's push goes through, and the second person sees:
 remote: waiting for lock on repository /path/to/repo held by '$server:$pid'
 remote: adding changesets
 remote: adding manifests
 remote: adding file changes
 remote: added $numcs changesets with $numchanges changes to $numfiles files

That is, the first list, which is the most interesting information as to why
the push is taking so long to take place, is not displayed until the whole
thing is finished.

In fact, it would be much more useful if the messages were displayed as they
arrive.

-- 
You are receiving this mail because:
You are on the CC list for the bug.