ede1b89252
Currently we were only specifying the block format. When adding with a custom hash function, even though we produced the right cids, IPFS did not know the hash function and ended up storing them using SHA256. Additionally, since NodeWithMeta serializes the CID, we do not need to carry a Format parameter (which specifies the Codec): it is already embedded. Tests have been added and BlockPut in ipfshttp now checks that the response's CID matches the data sent. This will catch errors like what was happening, but also any data corruption between cluster and IPFS during the block upload. |
||
|---|---|---|
| .. | ||
| adderutils | ||
| ipfsadd | ||
| sharding | ||
| single | ||
| adder_test.go | ||
| adder.go | ||
| util.go | ||