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
proof: re-try in HasProofs if some are unavailable
When CPU cycles are constrained (e.g. in CI), it can sometimes happen
that we:
- Import a proof into the multi archiver
- The multi archiver imports it into each backend
- The first backend notifies its subscribers after importing
- The custodian reacts to the notification and checks HasProof on
the multi archiver
- Because the other goroutine hasn't finished importing into all
backends, HasProof returns false
- The custodian only finishes the transfer once it receives the
notification from the second backend
All the above leads to the situation where the status "proof received"
is fired twice instead of just once, which causes the itests to fail
sometimes.
0 commit comments