Skip to content
Snippets Groups Projects
  1. Jan 16, 2020
  2. Jan 14, 2020
  3. Jan 21, 2020
  4. Feb 10, 2020
  5. Feb 09, 2020
  6. Jan 30, 2020
    • Raphaël Gomès's avatar
      rust-dirstatemap: cache non normal and other parent set · 83b2b829c94e
      Raphaël Gomès authored
      Performance of `hg update` was significantly worse since the introduction of
      the Rust `dirstatemap`. This regression was noticed by Valentin Gatien-Baron
      when working on a large repository, as it goes unnoticed for smaller
      repositories like Mercurial itself.
      
      This fix introduces the same getter/setter mechanism at `hg-core` level as
      for `set/get_dirs`.
      
      While this technique is, as previously discussed, quite suboptimal, it fixes an
      important enough problem. Refactoring `hg-core` to use the typestate
      pattern could be a good approach to improving code quality in a future patch.
      
      Differential Revision: https://phab.mercurial-scm.org/D8048
      83b2b829c94e
  7. Feb 07, 2020
  8. Feb 08, 2020
  9. Jan 31, 2020
  10. Feb 05, 2020
  11. Feb 07, 2020
  12. Feb 06, 2020
  13. Jan 24, 2020
  14. Jan 22, 2020
  15. Dec 13, 2019
  16. Sep 18, 2019
  17. Feb 07, 2020
  18. Jan 24, 2020
  19. Feb 04, 2020
  20. Jan 21, 2020
    • Matt Harbison's avatar
      lfs: enable workers by default · 87167caa2989
      Matt Harbison authored
      With the stall issue seemingly fixed, there's no reason not to use workers.  The
      setting is left for now to keep the test output deterministic, and in case other
      issues come up.  If none do, this can be converted to a developer setting for
      usage with the tests.
      
      Differential Revision: https://phab.mercurial-scm.org/D7963
      87167caa2989
    • Matt Harbison's avatar
      lfs: fix the stall and corruption issue when concurrently uploading blobs · 43eea17ae7b3
      Matt Harbison authored
      We've avoided the issue up to this point by gating worker usage with an
      experimental config.  See 10e62d5efa73, and the thread linked there for some of
      the initial diagnosis, but essentially some data was being read from the blob
      before an error occurred and `keepalive` retried, but didn't rewind the file
      pointer.  So the leading data was lost from the blob on the server, and the
      connection stalled, trying to send more data than available.
      
      In trying to recreate this, I was unable to do so uploading from Windows to
      CentOS 7.  But it reproduced every time going from CentOS 7 to another CentOS 7
      over https.
      
      I found recent fixes in the FaceBook repo to address this[1][2].  The commit
      message for the first is:
      
          The KeepAlive HTTP implementation is bugged in it's retry logic, it supports
          reading from a file pointer, but doesn't support rewinding of the seek cursor
          when it performs a retry. So it can happen that an upload fails for whatever
          reason and will then 'hang' on the retry event.
      
          The sequence of events that get triggered are:
           - Upload file A, goes OK. Keep-Alive caches connection.
           - Upload file B, fails due to (for example) failing Keep-Alive, but LFS file
             pointer has been consumed for the upload and fd has been closed.
           - Retry for file B starts, sets the Content-Length properly to the expected
             file size, but since file pointer has been consumed no data will be uploaded,
             causing the server to wait for the uploaded data until either client or
             server reaches a timeout, making it seem as our mercurial process hangs.
      
          This is just a stop-gap measure to prevent this behavior from blocking Mercurial
          (LFS has retry logic). A proper solutions need to be build on top of this
          stop-gap measure: for upload from file pointers, we should support fseek() on
          the interface. Since we expect to consume the whole file always anyways, this
          should be safe. This way we can seek back to the beginning on a retry.
      
      I ported those two patches, and it works.  But I see that `url._sendfile()` does
      a rewind on `httpsendfile` objects[3], so maybe it's better to keep this all in
      one place and avoid a second seek.  We may still want the first FaceBook patch
      as extra protection for this problem in general.  The other two uses of
      `httpsendfile` are in the wire protocol to upload bundles, and to upload
      largefiles.  Neither of these appear to use a worker, and I'm not sure why
      workers seem to trigger this, or if this could have happened without a worker.
      
      Since `httpsendfile` already has a `close()` method, that is dropped.  That
      class also explicitly says there's no `__len__` attribute, so that is removed
      too.  The override for `read()` is necessary to avoid the progressbar usage per
      file.
      
      [1] https://github.com/facebookexperimental/eden/commit/c350d6536d90c044c837abdd3675185644481469
      [2] https://github.com/facebookexperimental/eden/commit/77f0d3fd0415e81b63e317e457af9c55c46103ee
      [3] https://www.mercurial-scm.org/repo/hg/file/5.2.2/mercurial/url.py#l176
      
      Differential Revision: https://phab.mercurial-scm.org/D7962
      43eea17ae7b3
    • Matt Harbison's avatar
      lfs: add a method to the local blobstore to convert OIDs to file paths · 06de4a673f48
      Matt Harbison authored
      This is less ugly than passing an open callback to the `httpsendfile`
      constuctor.
      
      Differential Revision: https://phab.mercurial-scm.org/D7961
      06de4a673f48
  21. Jan 15, 2020
  22. Feb 05, 2020
  23. Feb 06, 2020
    • Kyle Lippincott's avatar
      py3: fully fix bundlepart.__repr__ to return str not bytes · 74172a234dd3
      Kyle Lippincott authored
      My previous fix did not fully fix the issue: it would attempt to use
      %-formatting to combine two strs into a bytes, which won't work. Let's just
      switch the entire function to operating in strs. This can cause a small output
      difference that will likely not be noticed since no one noticed that the method
      wasn't working at all before: if `id` or `type` are not-None, they'll be shown
      as `b'val'` instead of `val`. Since this is a debugging aid and these strings
      shouldn't be shown to the user, slightly rough output is most likely fine and
      it's likely not worthwhile to add the necessary conditionals to marginally
      improve it.
      
      Differential Revision: https://phab.mercurial-scm.org/D8091
      74172a234dd3
  24. Nov 17, 2019
  25. Nov 16, 2019
  26. Jan 25, 2020
  27. Nov 18, 2019
  28. Nov 16, 2019
  29. Jan 24, 2020
Loading