-
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
test: verifreg: Test notaries cannot remove datacap from verifreg #9557
test: verifreg: Test notaries cannot remove datacap from verifreg #9557
Conversation
3522905
to
830b58c
Compare
2a1d83c
to
ec53587
Compare
@arajasek Plz check that the most recent commit seems right to you |
Yup, i think that's fine! |
if err != nil { | ||
return nil, xerrors.Errorf("apply message failed: %w", err) | ||
} | ||
// Don't check for error here, we want to bubble it up, but also return ret as an InvocResult |
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.
ret
may be nil? @geoff-vball
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.
@simlecode you're right. I think this PR has the right behaviour #9582
Related Issues
Proposed Changes
Tests the fix implemented here. Verifreg notaries should not be able to remove datacap from the verifreg actor, because the verifreg's datacap balance should always equal the datacap of all pending allocations.
Additional Info
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps