Build is green

We decided to store manifests instead. T3594#74385

We decided to store manifests instead. T3594#74385

We decided to store manifests instead. T3594#74385

Build is green

Copy of an email I sent today:

rebase

squash commits

Build is green

Fix src/dst inversion, add regression test

Ok. Make sure you document it (in docs/), so we don't forget. It might be useful to add some rsync:// tests, but that's out of scope for this diff

Build is green

Build is green

rebase

• Add documentation for the remote storage backend

Copy of an email I sent on 2021-11-17:

Could you make sure that this dashboard https://grafana.softwareheritage.org/d/d3l2oqXWz/s3-object-copy?orgId=1 is not affected (or that its functionality can be replaced easily?)

You seem to have dropped the CONTENT_BYTES_METRIC ?

Good idea!

Build is green

In D6678#174111, @stsp wrote:

• add a test for conversion of a file which contains a Header keyword

• add a test for conversion of a file which contains a Header keyword

In D6678#174093, @stsp wrote:

And since our tests control the absolute paths to the test repositories they also control the expanded value of keywords like $Header$.
This means the tests would pass even without this fix in place. So I am not sure such a test would really be meaningful.

In D6678#174093, @stsp wrote:

This means the tests would pass even without this fix in place. So I am not sure such a test would really be meaningful.

In D6678#174084, @vlorentz wrote:

wow...

Good catch, thanks. Could you add a test for this (so we don't accidentally change it if we ever refactor the loader in the future)?

Thanks for the update.

All the nodes are updated

Good catch, thanks. Could you add a test for this (so we don't accidentally change it if we ever refactor the loader in the future)?

In D6691#174048, @vlorentz wrote:

Where is it called from?

Where is it called from?

Build has FAILED

Make repo.time an iso8601 string

Diff deployed through the v0.10.1

Waiting for the discussion on the lister diff to settle prior to accepting it (as this could impact the loader as well).

Awesome, thanks for the last updates. LGTM.

• search-esnode0 updated without errors

The upgrade by itself was made with the same command as explained previously.
The shard allocation was disabled during the process to avoid unnecessary movements of shard in the cluster

Build is green

Try to restart the build

Build is green

Amend commit, last fixes after review.

In D6395#174021, @swh-public-ci wrote:

Build has FAILED

Link to build: https://jenkins.softwareheritage.org/job/DLS/job/tests-on-diff/417/
See console output for more information: https://jenkins.softwareheritage.org/job/DLS/job/tests-on-diff/417/console

Build has FAILED

Updating D6395: rebase, update commit.

In D6395#174015, @ardumont wrote:

Not totally. I meant, can you please change the commit message (first line) to