35f60fd5eb
First, adding a logger argument allows the caller to have a logger already set up with whatever extra fields they want here. Secondly, we need to return the Outcome instead of a simple boolean so that it can be passed on to the Reporter later (need to make the right decision on increasing reputation vs decreasing it). Thirdly, we collect the cached reputation information from the overlay when creating the Orders, and return it from ReverifyPiece. This will allow the Reporter to determine what reputation-status fields need to be updated, similarly to how we include a map of ReputationStatus objects in an audit.Report. Refs: https://github.com/storj/storj/issues/5251 Change-Id: I5700b9ce543d18b857b81e684323b2d21c498cd8 |
||
---|---|---|
.. | ||
audit_test.go | ||
chore.go | ||
collector_test.go | ||
collector.go | ||
containment2_test.go | ||
containment_test.go | ||
containment.go | ||
cryptosource.go | ||
disqualification_test.go | ||
getshare_test.go | ||
integration_test.go | ||
pieces_test.go | ||
pieces.go | ||
queue.go | ||
reporter_test.go | ||
reporter.go | ||
reservoir_test.go | ||
reservoir.go | ||
reverifier_test.go | ||
reverifier.go | ||
reverify_test.go | ||
verifier_test.go | ||
verifier_unit_test.go | ||
verifier.go | ||
worker.go |