-
Notifications
You must be signed in to change notification settings - Fork 159
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
test: check compatibility for three more RPC calls #3698
Conversation
@@ -4,11 +4,16 @@ | |||
use super::*; | |||
use crate::shim::crypto::SignatureType; | |||
|
|||
// Lotus uses signature types under two names: `KeyType` and `SigType`. | |||
// `KeyType` can be deserialized from a string but `SigType` must always be an | |||
// integer. For more information, see |
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.
Shouldn't we add lenses for SignatureType
to cover these two cases?
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.
Not sure what you mean by this. Matching Lotus' behavior exactly will require some refactoring that is out of scope of this PR.
Summary of changes
Changes introduced in this pull request:
StateLookupID
StateNetworkVersion
WalletBalance
SignatureType
to always be encoded as an integer. Lotus requires this in certain places.Reference issue to close (if applicable)
Part of #3639
Other information and links
Change checklist