Change Details

As other loaders do, if any files is bigger than 100Mib, this content is not ingested in the swh archive. Implementation wise (storage related), this ends up referenced in the `content_missing` table (with associated hashes). For the deposit, those deposits should end up rejected. This will make sure that if a deposit is injected in the archive, its associated software source code will be cookable.

As other loaders do, if any files is bigger than 100Mib, this content is not ingested in the swh archive. Implementation wise (storage related), this ends up referenced in the `content_missing` table (with associated hashes). For the deposit, those deposits should end up rejected. This will make sure that if a deposit is injected in the archive, its associated software source code will be cookable (that and T1714 :)

As other loaders do, if any files is bigger than 100Mib, this content is not ingested in the swh archive. Implementation wise (storage related), this ends up referenced in the `content_missing` table (with associated hashes). For the deposit, those deposits should end up rejected. This will make sure that if a deposit is injected in the archive, its associated software source code will be cookable. (that and T1714 :)