looks sound to me, i'd add the 2 missing tests (which ensure we don't call stream_result* with page_token) since we are touching that part.

(^ for a while ;)

Status on this, after the recent refactoring we did with @olasd to simplify the actual
implementation (backend and journal client). There remains to:

(claiming i said ;)

(Claiming the task to find it back more easily through my activity view.)

Started in the same tmux session as the sourceforge ingestion.

It would probably make sense to set up a new worker instance for this to avoid interfering with the regular loading.

Smoke test it with local bitbucket repositories

that's next.

Smoke test it with remote repositories.

lgtm

Thanks for the heads up @ both of you.

Heads up, this is running slightly different now.

For history purpose readabillty, this must bev2.1 git-patched version (not a release per say).
A more recent version release which is a tag v2.1.0 [1] has been done built with the work
solving the work @olasd started with versioned extid.

Latest mercurial loader v2.1 deployed [1] [2]
We should be able to continue with this now.

Deployed \o/
Closing.

It's working but the check does not pass green [1]. As far as i could tell, the unsuccessful
event [1] is seen as failure by the check.

Still ongoing.

17:31:19 softwareheritage-scheduler@belvedere:5432=> select now(), visit_type, count(*) from listed_origins lo inner join listers l on l.id=lo.lister_id where l.name='gitlab' and l.instance_name='gitlab' group by visit_type order by count(
*) desc;
+-------------------------------+------------+---------+
|              now              | visit_type |  count  |
+-------------------------------+------------+---------+
| 2021-07-29 15:46:55.979469+00 | git        | 1747880 |
+-------------------------------+------------+---------+
(1 row)

The 'hg' ingestion started now that the latest loader mercurial got deployed.

At the end of it all though, the final production check end-to-end for mercurial origin should go green.

Like i said yesterday, lgtm.

From the staging webapp, we identify a revision [1]

by the way ^

Shipped the following modules to solve that problem:

• swh.model v2.7.0
• swh.storage v0.35.0
• swh.loader.mercurial v2.1.0