Change Details

As T847/T876 revealed, the bug fixed in the loader-core about the [[ https://forge.softwareheritage.org/rDLDBASEd74506f6b53dc3ffdae66e8446fe561d006a64f9 | misbehavior flushing step ]] could result in missing data. Those tasks only revealed the occurrences's target missing though. It's unfortunately possible that other objects might be missing (contents, directories, etc...). As we fixed quite some bugs in the loader-svn anyway and even though they should have been rescheduled, it seems more reasonable to reschedule all origins to make sure. At worst, it won't do anything. For the best, it will keep up with missing data. Note: Only the loader-svn should be impacted by those missing data since it's only recent that all loaders now derives from it. Loader-svn being historically the first one and using the flushing mechanism.

As T847/T876 revealed, the bug fixed in the loader-core about the [[ https://forge.softwareheritage.org/rDLDBASEd74506f6b53dc3ffdae66e8446fe561d006a64f9 | misbehavior flushing step ]] could result in missing data. Those tasks only revealed the occurrences's target missing though. It's unfortunately possible that other objects might be missing (contents, directories, etc...). As we fixed quite some bugs in the loader-svn anyway and even though they should have been rescheduled, it seems more reasonable to reschedule all origins to make sure. At worst, it won't do anything. At best, it will: - fill in the missing data. - gives a proper listing of origins with external-id - permit to ascertain bugged origins are no longer (again) Note: Only the loader-svn should be impacted by those missing data since it's only recent that all loaders now derives from it. Loader-svn being historically the first one and using the flushing mechanism.

As T847/T876 revealed, the bug fixed in the loader-core about the [[ https://forge.softwareheritage.org/rDLDBASEd74506f6b53dc3ffdae66e8446fe561d006a64f9 | misbehavior flushing step ]] could result in missing data. Those tasks only revealed the occurrences's target missing though. It's unfortunately possible that other objects might be missing (contents, directories, etc...). As we fixed quite some bugs in the loader-svn anyway and even though they should have been rescheduled, it seems more reasonable to reschedule all origins to make sure. At worst, it won't do anything. For theAt best, it will keep up with missing data.: - fill in the missing data. - gives a proper listing of origins with external-id - permit to ascertain bugged origins are no longer (again) Note: Only the loader-svn should be impacted by those missing data since it's only recent that all loaders now derives from it. Loader-svn being historically the first one and using the flushing mechanism.