A couple of suggestions inline.
And maybe even a typo in the status code to fix.

Can you please add the associated task id in the diff description?
(so one can browse to the related task more easily ;) ?

I'll let other have the last word (i'm going afk for a bit ;)

We can now see new maven origins [1] with multiple lists of artifacts [2]

@vsellier here is a rapid summary on:

And ingested:

Apr 29 13:38:51 worker3 python3[215979]: [2022-04-29 13:38:51,458: INFO/ForkPoolWorker-1] Task swh.loader.package.maven.tasks.LoadMaven[4ac12ab2-7749-4152-baa1-6bf06a587cad] succeeded in 74.83338255400304s: {'status': 'eventful', 'snapshot_id': '571e40dbc59f5f5238d981986211bcabde2d73d8'}

New schemed maven origins are getting listed now:

It's going the right way, thanks.

*thumbs up*, even better ;)

Arf, i reloaded the page (i was reviewing) but now lost the initial content of the diff.
You need to update back the diff with the range of commits you want to use.

lgtm, some suggestions inline.

We now have metadata in production as well [1].
So it's working.

one question inline.

After some tampering with the actual queue in scheduler0.staging (cleaning that up, it's staging so fine).
And limiting the number to less than 10k (100 is enough, way less workers).
We now have some github origins properly scheduled with their lister_name=github and lister_instance_name=github.
This now results in extrinsic metadata being fetched for those origins [1] (without me having to trigger the swh loader run cli).