Update to upstream version '1.9.1'
with Debian dir 19202ded7b36bfa220f2cacd15ec2aabcf19bcf2

It does not really make sense to average percentages, because they are unweighted,
and do not tell anything more than totals about individual runs.

Update to upstream version '1.9.0'
with Debian dir e8cc8071d3eadf2f9ced9823512976a761d2e5b8

In preparation for the removal of DVCSLoader from swh.loader.core,
as the git loader is the only one to use it anymore.

Update to upstream version '1.8.1'
with Debian dir 70839ed444fd62d05f581b3bd1c92cb174933e3d

base_snapshot_reverse_branches needs to contain all objects that
may be a snapshot target that the remote did not send to us.

Because we now use all snapshots to build the "have" list, such
targets include all targets of snapshots of "parent" origins,
not just the previous snapshot of the current origin.

This typically happens when a forge-fork pull branches from its
parent.

Resolves Sentry issue [[ https://sentry.softwareheritage.org/share/issue/1c08f5d764e7494e83ba254dc47f17af/ | SWH-LOADER-GIT-102 ]]

Only instances of (subclasses of) AbstractHttpGitClient have this attribute.

For other instances, we can consider it to be False, because the dumb
protocol only exists over HTTP(S).

This issue was found by mypy, thanks to the addition of type annotations
to changes in dulwich 0.20.36 affecting mypy's type inference.

Update to upstream version '1.8.0'
with Debian dir 79f3cb38e7ce46623822871ba88305aed21b1f76

Before this commit, determine_wants() used the origin's last snapshot
if any, or the closest parent's snapshot if not.

However, we noticed that many repositories that are very slow to load
are forks that were already visited, but their owner rebased it on the
parent since the last visit, causing potentially many commits to be
added to the origin.

This ensures we do not needlessly fetch these new commits when we
already loaded the parent.

Update to upstream version '1.7.0'
with Debian dir 50cb64eec4e789aa0e513e812f118dc5c68c1130

It will be used to debug why fork detection does not have the expected
speed-up in production.

Update to upstream version '1.6.0'
with Debian dir 5bf2d6898904e9a48a8f700f03daf0bc3fe1ee0d

self.parent_origins is set dynamically by the core loader at the
beginning of the load (before calling `prepare()`), using the right
metadata loaders.

Recent changes in swh-scheduler add new parameters to the celery tasks
produced from swh.scheduler.model.ListedOrigin instances.

So ensure to handle any new parameters by not hardcoding the expected
ones in task signatures.

Rename date parameter to visit_date in from disk loader tasks and
make it non mandatory.

Add new tests checking task parameters produced from ListedOrigin
instances do no raise error when attempting to create a git loader.

Related to T4187

Update to upstream version '1.5.0'
with Debian dir bd7d4902f5f2945c80970ac3694567b07bfcb2c0

That hook can be frustrating as it can discard a long commit message
if it finds a typo in it so better removing it.

Related to T3922