Skip to content
Snippets Groups Projects
  1. Oct 18, 2021
    • 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
  2. Oct 19, 2021
  3. Oct 13, 2021
  4. Oct 14, 2021
  5. Oct 19, 2021
  6. Oct 18, 2021
  7. Oct 19, 2021
  8. Oct 18, 2021
  9. Oct 19, 2021
  10. Oct 18, 2021
  11. Oct 15, 2021
    • Pierre-Yves David's avatar
      dirstate-v2: adds two flag to track the presence of some unrecorded files · dfc5a505
      Pierre-Yves David authored
      Right now, we don't record ignored or unknown files in the dirstate. However
      the structure would allow it. So we introduce two flags that can be used to
      clarify whether all unknown/ignored children are recorded or not. This will
      allow for more information to be stored in the future if this end up being
      relevant.
      
      Differential Revision: https://phab.mercurial-scm.org/D11682
      dfc5a505
    • Simon Sapin's avatar
      dirstate-v2: adds a flag to mark a file as modified · 1730b2fc
      Simon Sapin authored
      Right now, a files with a file system state that requires a lookup (same size,
      different mtime) will requires a lookup. If the result of that lookup is a
      modified files, it will remains ambiguous, requiring a lookup on the next status
      run too.
      
      To fix this, we introduce a dedicated flag in the new format. Such flag will
      allow to record such file as "known modified" avoiding an extra lookup later.
      
      As None of the associate code currently exist in the status code, we do the
      minimal implementation: if we read a dirstate entry with this flag set, we make
      it as "ambiguous" so that the next status code has to look it up. The same as it
      would have to without this flag existing anyway.
      
      Differential Revision: https://phab.mercurial-scm.org/D11681
      1730b2fc
  12. Oct 19, 2021
  13. Aug 27, 2021
  14. Oct 14, 2021
  15. Oct 18, 2021
  16. Oct 15, 2021
  17. Oct 14, 2021
  18. Oct 15, 2021
  19. Oct 12, 2021
  20. Oct 14, 2021
Loading