Fix prepare request in recovery message#765
Conversation
|
It can be set on the receiver side as well, somewhere in That's what NeoGo currently does in https://github.com/nspcc-dev/neo-go/blob/5eb4ba772f4d0e507d8a77699b3856f340c36fe8/pkg/consensus/recovery_message.go#L205 |
|
I agree with @roman-khimov , this will also be better for mainnet compatibility at this moment. |
|
@ZhangTao1596, I am double checking your commit, in fact, it will not affect payload serialization/de-serialization itself. |
vncoelho
left a comment
There was a problem hiding this comment.
@superboyiii, if possible try an extended test.
We use to have Unit Tests for consensus, that we created sometime ago.
@erikzhang, do you know why they were not ported for neo-modules?
That Akka tests can cover several cases, such as this.
I will. |
ValidatorIndexis uninitialized and unassigned inPrepareRequestMessageofRecoveryMessage. This will cause prepare request reverify failure when recovery.