The conclusions in the meeting were as follows:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Sep 28 2021
Sep 28 2021
Alphare added a comment to T3611: Define the mapping for Bazaar repositories/branches to the SWH data model.
swh-public-ci added a comment to D6348: Clarify local/remote heads type as those are hexadecimal bytes str.
Build is green
ardumont added inline comments to D6348: Clarify local/remote heads type as those are hexadecimal bytes str.
ardumont updated the diff for D6348: Clarify local/remote heads type as those are hexadecimal bytes str.
Fix type
ardumont renamed T3615: Adapt rabbitmq monitoring for bullseye from Adapt rabbimq monitoring for bullseye to Adapt rabbitmq monitoring for bullseye.
vsellier triaged T3616: Create a prometheus-statsd-exporter package for bullseye as Normal priority.
Harbormaster failed remote builds in B24054: Diff 23141 for D6348: Clarify local/remote heads type as those are hexadecimal bytes str!
swh-public-ci added a comment to D6348: Clarify local/remote heads type as those are hexadecimal bytes str.
Build has FAILED
ardumont updated the diff for D6348: Clarify local/remote heads type as those are hexadecimal bytes str.
Rebase
anlambert committed rDLDGd3976ca6504c: loader: Add support for dumb HTTP transfer protocol (authored by anlambert).
loader: Add support for dumb HTTP transfer protocol
Fix met's correct ip address
ardumont committed rSPSITE530e01d211ff: Adapt pgbouncer connection information for the provenance server (authored by ardumont).
Adapt pgbouncer connection information for the provenance server
ardumont updated the diff for D6365: Adapt postgresql connection information on the provenance server.
Rebase
ardumont updated the test plan for D6365: Adapt postgresql connection information on the provenance server.
ardumont updated the diff for D6365: Adapt postgresql connection information on the provenance server.
Use correct branch
ardumont requested review of D6365: Adapt postgresql connection information on the provenance server.
provenance: declare rabbitmq users
vsellier committed rSPPRIVC2362ec691041: Generate censored data from uncensored repository (authored by vsellier).
Generate censored data from uncensored repository
Build is green
Update: move comment inside if block
ardumont committed rSPSITEed1297dd6955: Adapt postgresql connection information on the provenance server (authored by ardumont).
Adapt postgresql connection information on the provenance server
ardumont requested review of D6363: Adapt postgresql connection information on the provenance server.
Update puppet facts
swh-public-ci added a comment to D6318: opam: Allow shared state between loader runs using multi-instance opam root.
Build is green
swh-public-ci added a comment to D6340: opam: Define a initialize_opam_root parameter for opam loader.
Build is green
swh-public-ci added a comment to D6318: opam: Allow shared state between loader runs using multi-instance opam root.
Build is green
ardumont updated the diff for D6318: opam: Allow shared state between loader runs using multi-instance opam root.
Fix diff
Build is green
Use the right diff id
ardumont updated the diff for D6318: opam: Allow shared state between loader runs using multi-instance opam root.
Actually update the diff?
swh-public-ci added a comment to D6318: opam: Allow shared state between loader runs using multi-instance opam root.
Build is green
ardumont retitled D6340: opam: Define a initialize_opam_root parameter for opam loader from opam: Define a production mode (default) to opam: Define a initialize_opam_root parameter for opam loader.
Update:
- Increase tests coverage: handle bare repo without pack files and check dumb repo can still be loaded if dulwich raises an exception in fetch_pack
- Improve comment
ardumont updated the diff for D6318: opam: Allow shared state between loader runs using multi-instance opam root.
Adapt according to suggestion
Broken link fix
Not a big fan of calling it production, because it implies it changes a bunch of settings in a non-granual way.
swh-public-ci added a comment to D6361: mercurial: Rename from_disk module to the main and official loader.
Build is green
Build is green
ardumont updated the diff for D6361: mercurial: Rename from_disk module to the main and official loader.
Rebase and adapt docstring according to suggestion
Adapt commit message
ardumont retitled D6360: mercurial: Drop legacy loader from mercurial: Drop dead code to mercurial: Drop legacy loader.
Not a big fan of calling it production, because it implies it changes a bunch of settings in a non-granual way.
s/dead code/the legacy loader/ in commit/diff title
ardumont added a comment to T3613: svn: An error occurred when running svnrdump and no exploitable dump file has been generated..
I was looking into it a bit more and realize that it's related to what you said
(origin not found).
Build is green
- add extensive testing
- remove special-casing of IntEnum and add converter for Directory.perms
- replace origin not in (Union,)
- fix a typo (raise False)
- add comment explaining why we don't check for dict and list
ardumont moved T3470: lister-sourceforge: Activate sourceforge origins when listed from Backlog to Weekly backlog on the System administration board.
ardumont moved T3487: Installation of the new provenance server from Weekly backlog to in-progress on the System administration board.
ardumont moved T3487: Installation of the new provenance server from Backlog to Weekly backlog on the System administration board.
ardumont closed T3568: Deploy opam lister/loader to production, a subtask of T3424: Opam support, as Resolved.
ardumont moved T3568: Deploy opam lister/loader to production from in-progress to deployed/landed/monitoring on the System administration board.
ardumont changed the status of T3568: Deploy opam lister/loader to production, a subtask of T3424: Opam support, from Open to Work in Progress.
ardumont changed the status of T3568: Deploy opam lister/loader to production from Open to Work in Progress.
That's done. The remaining part is about optimization. So closing.
The zfs pool and dataset are configured:
- pool configuration
## nvme drives pool #zpool create data mirror nvme-eui.36315030525005540025384500000003 nvme-eui.36315030525005800025384500000003 mirror nvme-eui.36315030525005620025384500000003 nvme-eui.36315030525005890025384500000003
ardumont closed T3457: Some git repositories are failing to be ingested because of MemoryError as Resolved.
I've deployed dulwich on our workers.
As a bonus, upstream merged the patch \o/.
swh-public-ci added a comment to D6361: mercurial: Rename from_disk module to the main and official loader.
Build is green
ardumont updated the diff for D6361: mercurial: Rename from_disk module to the main and official loader.
Fix missing old from_disk reference
ardumont requested review of D6361: mercurial: Rename from_disk module to the main and official loader.
vlorentz committed rDSNIPd8af1457ddb7: check_consistency.py: Add support for releases (authored by vlorentz).
check_consistency.py: Add support for releases