Skip to content
Snippets Groups Projects
  1. Nov 03, 2021
  2. Aug 25, 2021
  3. Oct 19, 2021
    • Pierre-Yves David's avatar
      dirstate-v2: freeze the on-disk format · bf11ff22
      Pierre-Yves David authored
      It seems the format as reached a good balance. With a core of new capabilities
      that motivated it initially and enough new feature and room for future
      improvement to be a clear progress we can set a milestone for.
      
      Having the format frozen will help the feature to get real life testing, outside
      of the test suite.
      
      The feature itself stay experimental but the config gains a new name to avoid
      people enable non-frozen version by default.
      
      If too many bugs are reported during the RC we might move the format back to
      experimental and drop its support in future version (in favor of a new one)
      
      Differential Revision: https://phab.mercurial-scm.org/D11709
      bf11ff22
  4. Nov 01, 2021
  5. Oct 22, 2021
  6. Oct 29, 2021
  7. Oct 28, 2021
    • Pierre-Yves David's avatar
      dirstate: make sure that status does not overlook the fallback flags · 50026041
      Pierre-Yves David authored
      Without this extra checks, file with fallback flags change as the only change
      would be overlooked.
      
      In the future we might store proper data in the dirstate and do less lookup.
      However, for now this will do to make sure that 6.0 is forward compatible with
      later version.
      
      Differential Revision: https://phab.mercurial-scm.org/D11729
      50026041
    • Pierre-Yves David's avatar
      dirstate: use a single closure for get_flags · 91f07430
      Pierre-Yves David authored
      The previous code was overlooking fallback when neither symlink not exec was
      supported.
      
      The number of "variants" is getting too high, so I am consolidating this in a
      single closure that should be easier to maintains.
      
      This also ensure that fallback flags are always taken into account.
      
      (they are not user code yet, but small experimentation shown that the feature
      was working as intended.)
      
      A a small side effect we need to check for symlink support more lazily and this
      show up in the test in a couple of places.
      
      Differential Revision: https://phab.mercurial-scm.org/D11728
      91f07430
  8. Apr 30, 2021
  9. Oct 26, 2021
  10. Oct 25, 2021
  11. Oct 23, 2021
  12. Oct 21, 2021
  13. Oct 20, 2021
  14. Oct 21, 2021
  15. Oct 20, 2021
  16. Oct 21, 2021
    • David Demelier's avatar
      hg: remove reserved identifiers · d8690805
      David Demelier authored
      Per 7.1.3 paragraph, from C draft:
      
      All identifiers that begin with an underscore and either an uppercase letter or
      another underscore are always reserved for any use.
      d8690805
  17. Oct 19, 2021
  18. Oct 20, 2021
  19. Oct 19, 2021
  20. Oct 18, 2021
    • Kyle Lippincott's avatar
      pyoxidizer: update README.md with several small fixes · 16c3fe46
      Kyle Lippincott authored
      Currently, pyoxidizer.bzl does not mention the git commit that should be checked
      out, so these instructions are a bit difficult to follow right now (impossible,
      technically), so I removed the instruction to `git checkout <Git commit>` and
      the admonition to use a specific version of PyOxidizer. I don't even know if the
      project currently builds with the "0.7.0-pre" version that was previously
      recommended.
      
      As fallout from that change to not "pin" to a specific PyOxidizer, I had to
      update the Python version to use when running the tests.
      
      While here, I added a recommendation to use `--release`, as the primary reason
      for this project is performance, and it may have been leaving some on the table
      to not have that there.
      
      Differential Revision: https://phab.mercurial-scm.org/D11698
      16c3fe46
    • Kyle Lippincott's avatar
      pyoxidizer: disable using in-memory resources · c900d962
      Kyle Lippincott authored
      It's possible that the errors are due to using an incompatible version of
      PyOxidizer; unfortunately the README.md file in this directory says to fetch a
      copy of PyOxidizer matching the commit in this pyoxidizer.bzl file, and yet the
      pyoxidizer.bzl file does not actually have a commit mentioned in it.
      
      By disabling in-memory modules, this appears to work on all platforms using the
      current head version of PyOxidizer, so let's disable them for now.
      
      Sample error (during `pyoxidizer build`):
      
      ```
      error[PYOXIDIZER_PYTHON_EXECUTABLE]: adding PythonExtensionModule<name=hgext.fsmonitor.pywatchman.bser>
      
      Caused by:
          extension module hgext.fsmonitor.pywatchman.bser cannot be loaded from memory but memory loading required
         --> ./pyoxidizer.bzl:140:5
          |
      140 |     exe.add_python_resources(exe.pip_install(["--verbose", ROOT]))
          |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ add_python_resources()
      
      
      error: adding PythonExtensionModule<name=hgext.fsmonitor.pywatchman.bser>
      
      Caused by:
          extension module hgext.fsmonitor.pywatchman.bser cannot be loaded from memory but memory loading required
      ```
      
      Differential Revision: https://phab.mercurial-scm.org/D11697
      c900d962
  21. Oct 19, 2021
  22. Oct 13, 2021
  23. Oct 14, 2021
  24. Oct 19, 2021
  25. Oct 18, 2021
Loading