Skip to content
Snippets Groups Projects
  1. Sep 01, 2018
  2. Aug 22, 2018
  3. Aug 26, 2018
  4. Sep 01, 2018
  5. Aug 25, 2018
  6. Aug 31, 2018
  7. Sep 01, 2018
    • Yuya Nishihara's avatar
    • Yuya Nishihara's avatar
    • Yuya Nishihara's avatar
      test-check-py3-compat: exclude thirdparty and cffi which are known to fail · 722eab64f1ed
      Yuya Nishihara authored
      Otherwise the following errors would be spilled out:
      
        mercurial/cffi/bdiff.py: error importing: <ImportError> cannot import
        name '_bdiff' (error at bdiff.py:*)
        mercurial/cffi/bdiffbuild.py: error importing: <ModuleNotFoundError> No
        module named 'cffi' (error at bdiffbuild.py:*)
        mercurial/cffi/mpatch.py: error importing: <ImportError> cannot import
        name '_mpatch' (error at mpatch.py:*)
        mercurial/cffi/mpatchbuild.py: error importing: <ModuleNotFoundError> No
        module named 'cffi' (error at mpatchbuild.py:*)
        mercurial/cffi/osutilbuild.py: error importing: <ModuleNotFoundError> No
        module named 'cffi' (error at osutilbuild.py:*)
        mercurial/thirdparty/concurrent/futures/_base.py: invalid syntax: invalid
        syntax (<unknown>, line *)
        mercurial/thirdparty/concurrent/futures/process.py: error importing:
        <SyntaxError> invalid syntax (_base.py, line 416) (error at __init__.py:*)
        mercurial/thirdparty/concurrent/futures/thread.py: error importing:
        <SyntaxError> invalid syntax (_base.py, line 416) (error at __init__.py:*)
        mercurial/thirdparty/zope/interface/_flatten.py: error importing:
        <ImportError> cannot import name 'Declaration' (error at _flatten.py:*)
      
      Some of them can be suppressed by building cffi modules for example, but
      I don't think it's worth keeping these modules covered by the compatibility
      checker.
      722eab64f1ed
    • Yuya Nishihara's avatar
      test-check-py3-compat: remove false output from "python3 check-py3-compat.py" · 875e635c201c
      Yuya Nishihara authored
      If python3 were python2, these errors would be reported, but we're running
      check-py3-compat.py on Python 3 here.
      875e635c201c
  8. Aug 01, 2018
  9. Aug 31, 2018
  10. Aug 30, 2018
  11. Aug 27, 2018
    • Gregory Szorc's avatar
      stringutil: teach pprint() to indent · 0f549da54379
      Gregory Szorc authored
      This will make data structure dumping in various places a bit
      easier to read and diff. Since I wanted this for `hg debugwireproto`
      output, I added indentation to it.
      
      A more advanced pretty printer implementation would conditionally
      add newlines if output is too long. But it is vastly simpler to
      be consistent and always add newlines when indenting.
      
      Again, I'm not crazy about the verbosity of the code and there is
      room to consolidate logic for "print a collection." But this isn't
      the most complicated code in the world and I'm not convinced it is
      worth doing.
      
      Differential Revision: https://phab.mercurial-scm.org/D4399
      0f549da54379
  12. Aug 22, 2018
  13. Jun 05, 2018
    • Boris Feld's avatar
      shelve: add an "internal" extra · 5f8282f368b2
      Boris Feld authored
      Keeping shelve changeset around increase the risk of collision with normal
      changesets. To prevent such collision and help with overall clarity, we add an
      'internal' key in extra that mark the changeset as created by "shelve".
      
      Node changes in tests are expected.
      5f8282f368b2
    • Boris Feld's avatar
      shelve: write metadata file on the fly if they are missing · 38373da1af02
      Boris Feld authored
      Keeping an explicit reference to the shelve node in order to reuse it directly
      if the unshelved is repeated (eg: unshelve --keep).
      38373da1af02
    • Boris Feld's avatar
      shelve: look for shelved node in the repository before unbundling · c67c94c0e7ae
      Boris Feld authored
      This prepares the version of shelve that would not strip the shelved node from
      the repository. If we have the node information, search for it in the
      repository and only fallback on unbundling if it is missing.
      
      To be able to find such nodes, we operate on an unfiltered repository.
      c67c94c0e7ae
    • Boris Feld's avatar
      shelve: handle shelved node on unfiltered repository · 6a71324cb68b
      Boris Feld authored
      To build a version of shelve that use hiding instead of stripping, we need
      shelve to be able to find these revisions. This it does not hurt the bundle
      version, so we introduce the necessary code in the relevant place.
      6a71324cb68b
  14. May 29, 2018
    • Boris Feld's avatar
      shelve: store shelved node in a new data file · da121c9dc0f2
      Boris Feld authored
      It is useful for a version of shelve not based on bundle and strip. Having
      more data does not hurt the bundle based case so we introduce it in all cases
      before doing more rework.
      
      We also keep storing the patch using another method.
      
      note: We could have this metadata file list all the file involved in the
      shelve and use that for cleanup. This would be more future proof than having a
      hard-coded list of file to purge. However, this is an adventure for another
      series.
      da121c9dc0f2
  15. Aug 05, 2018
  16. Aug 29, 2018
    • Pulkit Goyal's avatar
      copies: improve logic of deciding copytracing on based of config options · a41497b5117c
      Pulkit Goyal authored
      Few months ago or maybe a year ago, I imported Fb's heuristics based copytracing
      algorithms. While importing that, I renamed `experimental.disablecopytrace` with
      `experimental.copytrace` and the behavior of the new config option was like
      this:
      
        * "heuristics" : Fb's heuristic copytracing algorithm
        * "off" : copytracing is turned off
        * something else: copytracing is on
      
      This is the behavior right now also and this is bad because it hardcodes the
      string 'off' to turn off the copytracing. On big repositories, copytracing is
      very slow and people wants to turn copytracing off. However if the user sets it
      to 'False', 'Off', '0', none of them is going to disbale copytracing while they
      should.
      I lacked the understanding of why this can be bad when I coded it.
      
      After this patch, the new behavior of the config option will be:
      
        * "heuristics": Fb's heuristic copytracing algorithm
        * '0', 'false', 'off', 'never', 'no', 'NO', all the values which
          repo.ui.configbool() evaluates to False: copytracing in turned off
        * something else: copytracing is on
      
      Since 'off' still evaluates to copytracing being turned off, this is not BC.
      Also the config option is experimental.
      
      Differential Revision: https://phab.mercurial-scm.org/D4416
      a41497b5117c
  17. Aug 30, 2018
  18. Aug 29, 2018
  19. Aug 30, 2018
  20. Aug 27, 2018
Loading