Skip to content
Snippets Groups Projects
  1. Oct 19, 2018
  2. Oct 18, 2018
  3. Nov 17, 2016
  4. Oct 18, 2018
    • Matt Harbison's avatar
      tests: glob over a difference between Windows 7 and Window 10 · 5a81c4aa
      Matt Harbison authored
      The error value is 11001 on Windows 10.  I have no idea why it changed, but it
      seems unimportant.
      5a81c4aa
    • Matt Harbison's avatar
      py3: fix module imports in test-highlight.t · 3b84ef90
      Matt Harbison authored
      The hash changes are because the *.py file is committed to the repo.
      3b84ef90
    • Matt Harbison's avatar
      py3: fix module imports in tests, as flagged by test-check-module-imports.t · ef6cab79
      Matt Harbison authored
      I have no idea why these aren't flagged with python2.  I excluded
      test-highlight.t for now to make this easier to review- the changed code is
      committed to a repo, which has cascading changes on the rest of the test.
      
      There's a mix of bytes and str in the imports dict of contrib/import-checker.py
      that crashed it half way through listing out these errors.  I couldn't figure
      out how to fix that properly, so I was lazy and applied this on py3, to find the
      rest of the errors:
      
          diff --git a/contrib/import-checker.py b/contrib/import-checker.py
          --- a/contrib/import-checker.py
          +++ b/contrib/import-checker.py
          @@ -626,7 +626,12 @@ def find_cycles(imports):
               top.foo -> top.qux -> top.foo
               """
               cycles = set()
          -    for mod in sorted(imports.keys()):
          +    def sort(v):
          +        if isinstance(v, bytes):
          +            return v.decode('ascii')
          +        return v
          +
          +    for mod in sorted(imports.keys(), key=sort):
                   try:
                       checkmod(mod, imports)
                   except CircularImport as e:
      ef6cab79
  5. Oct 19, 2018
  6. Oct 18, 2018
    • Yuya Nishihara's avatar
      addremove: add "ui." prefix to message color keys · 824b687f
      Yuya Nishihara authored
      I don't like fully-colorized status/warning messages, and I want to disable
      them at all. If we'd supported a syntax like 'color.ui.*=none', I could
      easily turn addremove.added/removed off as well as ui.error. This patch is
      just for that.
      
      Since addremove colors aren't released yet, which were added at ddc1da134772,
      there are no compatibility concerns.
      824b687f
  7. Feb 09, 2017
  8. Oct 18, 2018
  9. Oct 16, 2018
  10. Oct 14, 2018
  11. Oct 18, 2018
  12. Oct 16, 2018
    • Matt Harbison's avatar
      py3: restore perfstartup() prior to b456b2e0ad9f on Windows · 1524c305
      Matt Harbison authored
      Otherwise the test errors out with:
      
          --- c:/Users/Matt/projects/hg_py3/tests/test-contrib-perf.t
          +++ c:/Users/Matt/projects/hg_py3/tests/test-contrib-perf.t.err
          @@ -184,6 +184,8 @@
             $ hg perfrevrange
             $ hg perfrevset 'all()'
             $ hg perfstartup
          +  'b'c:' is not recognized as an internal or external command,
          +  operable program or batch file.
             $ hg perfstatus
             $ hg perftags
             $ hg perftemplating
      1524c305
  13. Oct 18, 2018
  14. Sep 28, 2018
  15. Oct 17, 2018
  16. Oct 14, 2018
  17. Oct 05, 2018
    • Martin von Zweigbergk's avatar
      narrow: when widening, don't include manifests the client already has · 2c5835b4
      Martin von Zweigbergk authored
      When widening, we already don't include the changelog (since
      f1844a10ee19) and files that the client already has (since
      c73c7653dfb9). However, we still include all manifests needed for the
      new narrowspec. When using flat manifests, that means we resend all
      the manifests even though the client necessarily has all of them. For
      tree manifests, we unnecessarily resend the root manifests and any
      subdirectory manifests that the client already has.
      
      This patch makes it so we no longer resend manifests that the client
      already has. It does so by passing an extra matcher to the changegroup
      packer and it uses that for filtering out directories matching the old
      matcher's visitdir(). For consistency between directories and files,
      it also makes the filtering of files look at both old and new matcher
      rather than passing in a diff matcher as we did before.
      
      Differential Revision: https://phab.mercurial-scm.org/D4895
      2c5835b4
  18. Oct 17, 2018
  19. Oct 16, 2018
    • Kyle Lippincott's avatar
      revisions: when using prefixhexnode, ensure we prefix "0" · d916ed3c
      Kyle Lippincott authored
      Previously, if using `experimental.revisions.disambiguatewithin` (and it didn't
      include rev0), and '0' was the shortest identifier in that disambiguation set,
      we printed it as the shortest *without* a prefix. This was because we had logic
      to determine "if the prefix is a pure integer, but starts with 0, we don't need
      to prefix with 'x': 01 is not a synonym for revision #1", but didn't handle the
      case where prefix == 0 (which is a pure integer, and starts with 0... but it
      *is* "rev0").
      
      Differential Revision: https://phab.mercurial-scm.org/D5113
      d916ed3c
  20. Oct 03, 2018
  21. Sep 26, 2018
    • Pulkit Goyal's avatar
      streamclone: new server config and some API changes for narrow stream clones · af62936c
      Pulkit Goyal authored
      This patch introduces a new server config
      `experimental.server.stream-narrow-clones` which if set to True will advertise
      that the server supports narrow stream clones.
      
      This patch also pass on the includes and excludes from getbundle command to
      streamclone generation code.
      
      There is a test added to show that the includepats and excludepats are correctly
      passed.
      
      Upcoming patches will implement storage layer filtering for streamclones and
      then we can remove the temporary error and plug in the whole logic together to
      make narrow stream clones working.
      
      Differential Revision: https://phab.mercurial-scm.org/D5137
      af62936c
  22. Oct 10, 2018
    • Pulkit Goyal's avatar
      narrow: only send the narrowspecs back if ACL in play · cb516a85
      Pulkit Goyal authored
      I am unable to think why we need to send narrowspecs back from the server. The
      current state adds a 'narrow:spec' part to each changegroup which is generated
      when narrow extension is enabled. So we are sending narrowspecs on pull also.
      
      There is a problem with sending the narrowspecs the way we are doing it right
      now. We add include and exclude as parameter of the 'narrow:spec' bundle2 part.
      The the len of include or exclude string increase 255 which is obvious while
      working on large repos, bundle2 generation code breaks. For more on that refer
      issue5952 on bugzilla.
      
      I was thinking why we need to send the narrowspecs back, and deleted the
      'narrow:spec' bundle2 part generation code and found that only narrow-acl test
      has some failure.
      
      With this patch, we will only send the 'narrow:spec' bundle2 part if ACL is
      enabled because the original narrowspecs in those cases can be a subset of
      narrowspecs user requested.
      
      There are phase related output change in couple of tests. The output change
      shows that we are now dealing in public phases completely. So maybe sending the
      narrow:spec bundle2 part was preventing phases being exchanged or phase bundle2
      data being applied.
      
      Differential Revision: https://phab.mercurial-scm.org/D4931
      cb516a85
Loading