d1700dbe81
The Allocations of a pin that has been added with default replication factor are kept even when the replication factor turns out to be -1. This resulted in the Status(cid) code skipping calls to a number of peers and setting the pin directly as REMOTE. The fix, on one side makes sure Allocations is always nil when the replication factor is -1. On the other size, lets the globalPinInfoCid method check the replication factor value, rather than the number of allocations to decide if any nodes are bound to be remote. On the plus side, the pin tracker used the IsRemotePin method, which uses the replication factor, so things were pinned even if the Status(cid) method shows them as remote. |
||
|---|---|---|
| .. | ||
| ipfsproxy | ||
| pb | ||
| rest | ||
| add_test.go | ||
| add.go | ||
| types_test.go | ||
| types.go | ||
| util.go | ||