-
Notifications
You must be signed in to change notification settings - Fork 144
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
feat(rpc): implement Filecoin.StateSectorExpiration #4339
Conversation
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 good to me. The handler code is a bit convoluted due to a bunch of nesting, but thankfully not a lot of lines, so I don't think there's real need for any kind of refactoring.
let success = match (&forest_status, &lotus_status) { | ||
(TestSummary::Valid, TestSummary::Valid) | ||
| (TestSummary::Timeout, TestSummary::Timeout) => true, | ||
(TestSummary::Rejected(ref reason_forest), TestSummary::Rejected(ref reason_lotus)) |
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.
This will make the tests pass even if both inputs to Forest and Lotus are accidentally malformed, no? Do you think it'd be safer to explicitly declare tests that should (could) fail and only allow them to do so?
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.
Fixed.
Summary of changes
Changes introduced in this pull request:
implement Filecoin.StateSectorExpiration
Reference issue to close (if applicable)
Closes #4334
Other information and links
Change checklist