You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If running IPFS 0.4.21 and IPFS Cluster 0.10.1, due to the dependencies being used by IPFS Cluster 0.10.1, any pin requests will generally display the following error when running ipfs-cluster-ctl status
PIN_ERROR: expected to find the pin in the response
This issue appears to be happening because go-ipfs is handling IPFS CID's in base32, while IPFS Cluster is handling CID's in base58. So far it doesn't appear that this issue is leading to any data loss, just a lot of noise.
Additionally it also looks like in certain cases, the following error may also be displayed:
PIN_ERROR: the item is unexpectedly not pinned on IPFS
However this is not actually the case, as said CID is pinned across all the nodes in my cluster. This appears to be due to the same issue mentioned previously.
The text was updated successfully, but these errors were encountered:
Additional information:
Describe the bug:
If running IPFS 0.4.21 and IPFS Cluster 0.10.1, due to the dependencies being used by IPFS Cluster 0.10.1, any pin requests will generally display the following error when running
ipfs-cluster-ctl status
This issue appears to be happening because go-ipfs is handling IPFS CID's in base32, while IPFS Cluster is handling CID's in base58. So far it doesn't appear that this issue is leading to any data loss, just a lot of noise.
Additionally it also looks like in certain cases, the following error may also be displayed:
However this is not actually the case, as said CID is pinned across all the nodes in my cluster. This appears to be due to the same issue mentioned previously.
The text was updated successfully, but these errors were encountered: