-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix off by one tipset in searchBackForMsg #4367
Conversation
This way we will return the tipset the message was executed in Signed-off-by: Jakub Sztandera <kubuxu@protocol.ai>
Signed-off-by: Jakub Sztandera <kubuxu@protocol.ai>
bf25322
to
ce548c8
Compare
var ser []byte | ||
var err error | ||
if sm.Signature.Type == crypto.SigTypeBLS { | ||
// BLS chain message length doesn't include signature | ||
ser, err = sm.Message.Serialize() | ||
} else { | ||
ser, err = sm.Serialize() | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a fix for a different issue, mildly fishy consensus-wise, though looking at usages I believe it's fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it is a fix for the mempool. Doesn't touch consensus as we have no signed BLS message in VM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks
This way we will return the tipset the message was executed in