$commits
$commits : int
What one reindex rebuilt.
Read to answer the question the operation exists for: is the index back, and does it describe the same history the bucket holds. Skipped counts are the part to look at - an object the walk could not use is a restore target that is not coming back, and reporting it as a success would be worse than failing.
__construct(int $commits = 0, int $packs = 0, int $frames = 0, int $references = 0, int $segments = 0, int $skipped = 0, list$problems = [], float $seconds = 0.0, int $placements = 0, int $branches = 0) : mixed
Constructs a report.
| int | $commits | Commit rows written. |
| int | $packs | Pack objects read for their frame directories. |
| int | $frames | Frame rows written. |
| int | $references | Reference counts attributed by reading the segments the refs reach. |
| int | $segments | Segment manifests read. |
| int | $skipped | Objects the walk could not use. |
| list |
$problems | One line per skipped object, naming the key and the reason. |
| float | $seconds | How long the rebuild took. |
| int | $placements | Object placements recorded, on a store spread across several buckets. Zero on a store with one destination, where every object is in the only place it could be. |
| int | $branches | Branch rows written from the refs and the metadata objects beside them. |