stuff related to https://forge.softwareheritage.org/diffusion/DLSCG/
Details
Jan 8 2023
Oct 19 2022
May 23 2022
Mar 11 2022
Triggered back a run and it seemed to have run well:
Mar 11 12:23:15 worker14 python3[2494505]: [2022-03-11 12:23:15,252: INFO/MainProcess] Received task: swh.lister.cgit.tasks.CGitListerTask[e7674643-c7ca-4ae1-910e-9ea24e8c2335] Mar 11 12:23:17 worker14 python3[2961235]: [2022-03-11 12:23:17,950: INFO/ForkPoolWorker-7] Task swh.lister.cgit.tasks.CGitListerTask[e7674643-c7ca-4ae1-910e-9ea24e8c2335] succeeded in 2.3799873050302267s: {'pages': 1, 'origins': 177}
Sentry issue: SWH-LISTER-4V
Should be a matter of updating such task with:
Oct 22 2021
Fixed in swh-lister v2.2.0 and deployed to production, closing this.
Oct 11 2021
Jan 29 2021
Build is green
Rebase
Looks good to me !
Build is green
Adapt according to review:
- Add more cgit instance samples
- Rework docstring
- Rework url computation a bit
Build is green
Adapt according to review
The current implementation will not work for most cases where the base cgit URL and the base clone URL differs (see inline comment).
I guess you mean that some cgit origin URLs previously loaded into the archive will not be the same if
the approach in that task is implemented ?
Analyzing further the suggestions using the deprecated swh-lister cache db table as data
point (production data) [1], 3 instances so far will generate sometimes wrong origin
urls with the suggested approach.
Analyzing further the suggestions using the deprecated swh-lister cache db table as data
point (production data) [1], 3 instances so far will generate sometimes wrong origin
urls with the suggested approach.