consensus: use our implementations of Recovery* messages
While decoding payload, local implementations of Recovery* messages were used, but when creating RecoveryMessage inside dBFT library default NewRecoveryMessage was invoked. This lead to parsing errors.
This commit is contained in:
parent
d234a1e718
commit
390bf58f97
1 changed files with 2 additions and 0 deletions
|
@ -139,6 +139,8 @@ func NewService(cfg Config) (Service, error) {
|
|||
dbft.WithNewPrepareResponse(func() payload.PrepareResponse { return new(prepareResponse) }),
|
||||
dbft.WithNewChangeView(func() payload.ChangeView { return new(changeView) }),
|
||||
dbft.WithNewCommit(func() payload.Commit { return new(commit) }),
|
||||
dbft.WithNewRecoveryRequest(func() payload.RecoveryRequest { return new(recoveryRequest) }),
|
||||
dbft.WithNewRecoveryMessage(func() payload.RecoveryMessage { return new(recoveryMessage) }),
|
||||
)
|
||||
|
||||
if srv.dbft == nil {
|
||||
|
|
Loading…
Reference in a new issue