Just to be sure: test_pipeline() from test_cli.py is now run with all new passes as well, and as such it also testes the LLP step(s), correct?
It seems that way to me because test_pipeline() seems to be running all passes, but I'd like this to be double-checked before landing.

I've tried replacing the content of foo.txt with something unknown to the archive (random garbage) and the sunburst rendering still shows 100.0%.
So it could also be a rounding error instead.
Either way, it is misleading and should be fixed.

<3

the cooking has completed now

In T1538#73659, @moranegg wrote:

Is the request for regular pulling?
If yes, it should be added for visibility on the home page of the archive.
If no, it should be clear this is a one shot thing.

Where is the documentation on how to access the new read-only object storage?
(hint hint :-))

Nope, if loaded with only one direction, traversals will only be possible in the loaded direction.
This will essentially be a trade-off setting for people who cannot (or doesn't want to) load both direction.
It is fine to fail (gracefully, with an error) traversals requested in a direction that corresponds to a non-loaded graph.

Thanks for the summaries @olasd, both here and on list.
I've followed up on list.

rebase

@vsellier sure, and thanks! "Basic auth" is in the HTTP sense, right? So username/password pairs that we can add on demand, correct?

In D6479#168150, @anlambert wrote:

There is a typo in commit message: s/bib/bin/.