Description: Update the Spade RB to also test that Bitswap-accessible CIDs are also advertised to IPNI by the storage providers we are retrieval testing. For each CID that is retrieval tested by the Bitswap worker, we also need to ensure that the IPNI has a record for this SP<->CID
We need to test how quick/expensive the IPNI lookup operation is. If it's quick and cheap, then we can do it "in-line" as part of the Bitswap retrieval test itself. If it's slow and/or expensive, then we should write the list of CIDs to a separate database table, and build out a separate "IPNI Worker" to check them asynchronously.
The output for this should be an IPNI Lookup Result (separate from the Bitswap pass/fail result) for the given CID for the given SP.
Description: Update the Spade RB to also test that Bitswap-accessible CIDs are also advertised to IPNI by the storage providers we are retrieval testing. For each CID that is retrieval tested by the Bitswap worker, we also need to ensure that the IPNI has a record for this SP<->CID
We need to test how quick/expensive the IPNI lookup operation is. If it's quick and cheap, then we can do it "in-line" as part of the Bitswap retrieval test itself. If it's slow and/or expensive, then we should write the list of CIDs to a separate database table, and build out a separate "IPNI Worker" to check them asynchronously.
The output for this should be an IPNI Lookup Result (separate from the Bitswap pass/fail result) for the given CID for the given SP.
ETA: YYY-MM-DD Maintainer:
Known dependencies:
View this starmap at: