I'm really not a fan of erb templates for yaml configuration files (specifically, seed_provider: <%= @config["seed_provider"].to_yaml().delete_prefix("---") %> is pretty jarring). I agree that inlining the full default config was not a good idea, though.

Looks good, thanks.

LGTM, thanks!

Looks much better indeed!

Is there a way to use a "service" token rather than one tied to an individual account?

Shouldn't we add privileged topics too?

This could probably be logger.exception instead of an unqualified logging.exception

Looks like there's many more repos that should be visitable but aren't:

Great, thanks

updated query running:

As usual, I'm uneasy with the (general) idea of manually handling some repositories to resorb one bit of lag. This will only increase lag in another area that we will want to cover next. Rinse, repeat.

Not sure I understand the insistence on using variables, but *shrug*

I would suggest only matching on line beginnings, so that we can update the values and possibly disable swap if we find it problematic.
I've added escaping of the regexps.

Let's use file_line resources instead of using a template which will be out of date 28 seconds after the change is pushed.

The origin extrinsic metadata indexer only runs on a single file at a time, so I don't think it needs to run alone on dedicated hosts.

FWIW I've also started the provenance storage server as a systemd system service now.

I've granted mmca access to the production journal for user swh-provenance-mmca.

I've added an autossh-mmca.service unit on belvedere to have a reverse tunnel from localhost@mmca:5345 -> localhost@belvedere:5432.

Looks fine to me, but the SVG wants the font (Alegrya Sans SC) to be installed on your system. We might want to force that to be splines instead of text.

Looks good to me, thanks!

In D8106#210862, @ardumont wrote:

or you could edit on the template directly? [1]

[1] https://hedgedoc.softwareheritage.org/6YKT5osoST-amJQ0MusH2Q?edit

Looks like some copy-and-waste happened here, sorry I hadn't noticed at first !

Nice, thanks!

Welp.

Maybe a new cli test for the revision journal client would be nice

LGTM, thanks!

I'm slightly surprised by the change of signature for translate_directory_intrinsic_metadata without change to the docstring. AFAICT this function now does the detection itself, so maybe it deserves an update.

lol

It looks like the rabbitmq provenance storage server, which is run within the pytest context through multiprocessing (so forks a bunch of python processes in the pytest run context), interacts poorly with the confluent-kafka library (which is used in the swh.journal fixtures, and brings up a bunch of internal threads).

Drop useless rabbitmq server change

Ensure coverage results are kept incrementally