Skip to content

report: cover upload-based migrations, not just aggregates #73

Description

@SgtPooki

Description

report reconciles the aggregates table against on-chain pieces, so it covers the provider-pull path only. A migration done with upload (#71) records its state in the uploads table, which report never reads — running it after an upload-based migration reports nothing committed.

Impact

The campaign runbook cannot use report for verification and instead tells agents to check the explorer and spot-check retrievals by hand. That works, but the on-chain reconciliation and --check-ipni sampling report already implements are exactly what verification wants.

Proposed next step

Teach report to read the uploads table too: reconcile each (piece, provider) row against activePieceCids of its data set, and keep the IPNI sampling unchanged.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    📌 Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions