Mitigate noise from py-ipfs-api due to its mis-handling of 0-length payloads per #485 #572
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue of using py-ipfs-api to
add_bytes()
of zero-length payloads is still an outstanding issue per ipfs-shipyard/py-ipfs-http-client#137. This causes a lot of noise by the ipwb indexer when encountering these records, like when indexingsamples/warcs/IAH-20080430204825-00000-blackbook.warc.gz
.This PR prevents these records from being attempted to be pushed into IPFS using py-ipfs-api. When ipfs-shipyard/py-ipfs-http-client#137 is fixed, we can change the logic but for now, this will short-circuit the attempt from ipwb.