check supports time-limited partial checks and also writes checkpoints even when not requesting a partial check.
such a checkpoint is a marker telling the last pack id it checked, so the next run can skip all packs up to there (requires sorted pack listing).
problem: if in the meantime new packs get added, the continued check might not check them if their pack id is "before" the marker.
solution: rather persist a set of checked pack ids and use that for skipping.
check supports time-limited partial checks and also writes checkpoints even when not requesting a partial check.
such a checkpoint is a marker telling the last pack id it checked, so the next run can skip all packs up to there (requires sorted pack listing).
problem: if in the meantime new packs get added, the continued check might not check them if their pack id is "before" the marker.
solution: rather persist a set of checked pack ids and use that for skipping.