Skip to content
Snippets Groups Projects
  1. Jan 07, 2024
  2. Nov 23, 2023
  3. Jan 07, 2024
  4. Jan 06, 2024
  5. Jan 04, 2024
  6. Nov 23, 2023
  7. Jan 04, 2024
  8. Nov 23, 2023
  9. Dec 29, 2023
  10. Nov 23, 2023
    • Pierre-Yves David's avatar
      delta-find: use "-1" as depth snapshot-dept for non snapshot in debug · 0d92d62ecde0
      Pierre-Yves David authored
      This will help do distinct full snapshot (level 0) and normal delta (not a snapshot, no snapshot level)
      0d92d62ecde0
    • Pierre-Yves David's avatar
      delta-find: fix the computation of the `prev` value · 2e169a222e63
      Pierre-Yves David authored
      The previous computation was "wrong" it always used the tiprev, even when computing a delta in a non-append case (mostly benchmark).
      
      This never produced wrong delta on disk, but would misled debug or performance command. Since it does not have any actual user impact, I did not put this on stable.
      
      With the code fixed we can now use revisions in some search and it makes the
      test display more interesting behavior since the algorithm has more to work
      with.
      2e169a222e63
  11. Dec 22, 2023
  12. Nov 23, 2023
  13. Nov 20, 2023
  14. Dec 22, 2023
  15. Jan 11, 2024
  16. Jan 03, 2024
    • Georges Racinet's avatar
      pycompat: fix bytestr(bytes) in Python 3.11 · f0e7d51bb454
      Georges Racinet authored
      In Python 3.10, the `bytes` type itself does not have a `__bytes__`
      attribute, but it does in 3.11. Yet `bytes(bytes)` does not give
      the wished output, so we have to add an exceptional case.
      
      The added case in the doctest reproduces the problem with Python 3.11.
      
      Impact: error treatment in expressions such as `repo[b'invalid']` gets
      broken.
      f0e7d51bb454
  17. Jan 08, 2024
    • Anton Shestakov's avatar
      contrib: add a set of scripts to run pytype in Docker · 87bfd1703597
      Anton Shestakov authored
      Having a simple way to run pytype for developers can massively shorten
      development cycle. Using the same Docker image and scripts that we use on our
      CI guarantees that the result achieved locally will be very similar to (if not
      the same as) the output of our CI runners.
      
      Things to note: the Dockerfile needs to do a little dance around user
      permissions inside /home/ci-runner/ because:
      
      - on one hand, creating new files on the host (e.g. .pyi files inside .pytype/)
        should use host user's uid and gid
      
      - on the other hand, when we run the image as uid:gid of host user, it needs to
        be able to read/execute files inside the image that are owned by ci-runner
      
      Since local user's uid might be different from ci-runner's uid, we execute this
      very broad chmod command inside /home/ci-runner/, but then run the image as the
      host user's uid:gid.
      
      There might be a better way to do this.
      87bfd1703597
Loading