TarballDirectoryLoader: Ingest tarball as package loaders do
This is source of discrepancy for origins with type tarball-directory which do not have the top-level directory. This also matches how the package loader are currently ingesting artifacts [1] In terms of data, this will change the visit snapshot and the extid mapping. As a result, the tarball directory loader have now an extid_version set to 1 (it was 0, the default). In terms of ui browsing, this won't change since the webapp already has heuristic to naturally skip the unique top-level directory. [1] https://gitlab.softwareheritage.org/swh/devel/swh-loader-core/-/blob/master/swh/loader/package/loader.py?ref_type=heads#L829-837 Refs. swh/infra/sysadm-environment#5222
Showing
- swh/loader/core/loader.py 7 additions, 11 deletionsswh/loader/core/loader.py
- swh/loader/core/tests/test_loader.py 22 additions, 2 deletionsswh/loader/core/tests/test_loader.py
- swh/loader/core/utils.py 1 addition, 1 deletionswh/loader/core/utils.py
- swh/loader/tests/__init__.py 4 additions, 2 deletionsswh/loader/tests/__init__.py
Loading
Please register or sign in to comment