Build is green

Make sure we try to fill in the queues space space is still available, prior to pass to
the next visit type.

Build is green

That sounds about right to me!

The diff (D6448) has been updated to support a basic authentication for the public part. The internal access will remain possible without any authentication.

fix a typo

Add basic authentication support and activate it in staging too
(main description will be updated accordingly)

drop the computation done in the archive coverage part for those origins.

Build is green

lgtm

lgtm

Plan to fix this:

• land diff D6539
• package and deploy it (within swh.lister v2.2.0)
• update the origins in the scheduler backend (tables listed_origins, scheduler metrics, origin_visit_stats) [1] [2]
• ensure cran origins are scheduled (scheduler runner in place)
• ensure the swh-worker@loader_cran service does its job
• Schedule a recent listing after all fixes
• D6544: drop the computation done in the archive coverage part for those origins.

I've tried to generate a server config, out of the HPE ProLiant DL380 G10 (Intel based) and DL385 G10+ (AMD EPYC based) configs available on MATINFO5.

Ah, @anlambert found the issue, tar type instead of cran type. The result of the
following queries [1] should be the opposite... no tar origins, only cran ones.

That makes sense for almost everything.

Great news: of the 469k corrupt SVN revisions, all but 14 (yes, 14) can be fixed simply by adding 1 microsecond to their timestamp.

I need to update a bit the logic to actually match the algo described in the task.
Notably the fill in the queue while there is still room part.

I came across a rather small repository [1] which i believe raise the same issue.
So it may help to keep its reference to ease the testing of the improvment discussed here.
Feel free to dismiss if not that useful.

fine with me.

rebase

Adapt according to discussion

Build is green

As the new kafka is active since a couple of day, a mirror was restored from it and everything seems to be ok, journal0(stopped since the migration is done) was removed from proxmox.

typo fixes; added doc links

arf wrong issue, restoring statuses

EDITED: removed, commented on the wrong taks

In D6537#169707, @anlambert wrote:

This is the same diff as D6536 no ?

This is the same diff as D6536 no ?

Build is green

Build is green

This is the same diff as D6536 no ?

Use correct repo to update diff...

The issue has been fixed upstream and will be part of next pip release.

Reword commit message