[#486] innerring: Use fee provider and notary disabled flag in processors
Processors that use `invoke` package to make chain invocation should provide fee config and client with enabled or disabled notary support. If notary support is disabled, then functions from `invoke` package will perform ordinary method invocation with extra fee. Processors that use `morph/client` wrappers should check `notaryDisabled` flag to call corresponding wrapper function. Netmap processor omits some actions during validator syncronization if notary is disabled. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
This commit is contained in:
parent
91a1896b8b
commit
f2562e8c47
16 changed files with 111 additions and 38 deletions
|
@ -27,7 +27,12 @@ func (np *Processor) processNewEpoch(epoch uint64) {
|
|||
}
|
||||
|
||||
if epoch > 0 { // estimates are invalid in genesis epoch
|
||||
err = np.containerWrp.StartEstimationNotary(epoch - 1)
|
||||
if np.notaryDisabled {
|
||||
err = np.containerWrp.StartEstimation(epoch - 1)
|
||||
} else {
|
||||
err = np.containerWrp.StartEstimationNotary(epoch - 1)
|
||||
}
|
||||
|
||||
if err != nil {
|
||||
np.log.Warn("can't start container size estimation",
|
||||
zap.Uint64("epoch", epoch),
|
||||
|
@ -52,7 +57,7 @@ func (np *Processor) processNewEpochTick() {
|
|||
nextEpoch := np.epochState.EpochCounter() + 1
|
||||
np.log.Debug("next epoch", zap.Uint64("value", nextEpoch))
|
||||
|
||||
err := invoke.SetNewEpoch(np.morphClient, np.netmapContract, nextEpoch)
|
||||
err := invoke.SetNewEpoch(np.morphClient, np.netmapContract, np.feeProvider, nextEpoch)
|
||||
if err != nil {
|
||||
np.log.Error("can't invoke netmap.NewEpoch", zap.Error(err))
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue