Skip to content
Snippets Groups Projects
  1. Sep 04, 2018
  2. Jan 18, 2018
    • Jörg Sonnenberger's avatar
      wireproto: support for pullbundles · aacfca6f
      Jörg Sonnenberger authored
      Pullbundles are similar to clonebundles, but served as normal inline
      bundle streams. They are almost transparent to the client -- the only
      visible effect is that the client might get less changes than what it
      asked for, i.e. not all requested head revisions are provided.
      
      The client announces support for the necessary retries with the
      partial-pull capability. After receiving a partial bundle, it updates
      the set of revisions shared with the server and drops all now-known
      heads from the request list. It will then rerun getbundle until
      no changes are received or all remote heads are present.
      
      Extend badserverext to support per-socket limit, i.e. don't assume that
      the same limits should be applied to all sockets.
      
      Differential Revision: https://phab.mercurial-scm.org/D1856
      aacfca6f
  3. Feb 24, 2018
  4. Jun 30, 2017
  5. Apr 17, 2017
  6. Apr 14, 2017
    • Gregory Szorc's avatar
      tests: add tests for poorly behaving HTTP server · c85f19c6
      Gregory Szorc authored
      I've spent several hours over the past few weeks investigating
      networking failures involving hg.mozilla.org. As part of this, it
      has become clear that the Mercurial client's error handling when
      it encounters network failures is far from robust.
      
      To prove this is true, I've devised a battery of tests simulating
      various network failures, notably premature connection closes. To
      achieve this, I've implemented an extension that monkeypatches the
      built-in HTTP server and hooks in at the socket level and allows
      various events to occur based on config options. For example, you
      can refuse to accept() a client socket or you can close() the socket
      after N bytes have been sent or received. The latter effectively
      simulates an unexpected connection drop (and these occur all the
      time in the real world).
      
      The new test file launches servers exhibiting various "bad" behaviors
      and points a client at them. As the many TODO comments in the test
      call attention to, Mercurial often displays unhelpful errors when
      network-related failures occur. This makes it difficult for users
      to understand what's going on and difficult for server administrators
      to pinpoint root causes without packet tracing.
      
      Upcoming patches will attempt to fix these error handling
      deficiencies.
      c85f19c6
Loading