[Bug 4784] New: Bundle2 client handles dropped HTTP(S) connections poorly, with cryptic error messages

[mercurial-bugs at selenic.com]

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

          Priority: normal
            Bug ID: 4784
                CC: mercurial-devel at selenic.com,
                    pierre-yves.david at ens-lyon.org
          Assignee: bugzilla at selenic.com
           Summary: Bundle2 client handles dropped HTTP(S) connections
                    poorly, with cryptic error messages
          Severity: bug
    Classification: Unclassified
                OS: All
          Reporter: gabor.stefanik at nng.com
          Hardware: All
            Status: UNCONFIRMED
           Version: 3.5
         Component: bundle2
           Product: Mercurial

Occasionally during a HTTP(S) clone/push/pull operation, the connection may end
prematurely. With the old bundle format, this error is reported to the user in
a meaningful way. However, when using bundle2, a misguided attempt is made to
parse the remaining input stream in an out-of-sync way, causing strange
internal errors to be reported.

We should either use HTTP resuming or some other method to recover from such a
situation, or at least report it meaningfully to the user.

Because of another problem where HTTP communication completely stops during the
"Adding manifest" phase of a clone (which can take very long especially when
converting to generaldelta), this bug often appears when trying to clone very
large repositories with long, heavily branched histories.

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