-
Notifications
You must be signed in to change notification settings - Fork 1k
Plug BlockSpaceAllocator logic into ProcessProposal
#895
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
Plug BlockSpaceAllocator logic into ProcessProposal
#895
Conversation
| AllocationError = 8, /* NOTE: keep these values in sync with | ||
| * [`ErrorCodes::is_recoverable`] */ |
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.
ErrorCodes::is_recoverable should be matching on this enum rather than returning (self as u32) <= 3, to enforce this (related to this NOTE but not the PR itself though, we shouldn't change this as part of this PR)
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.
that's how it was defined in ProcessProposal before, this is_recoverable() method came from a ProcessProposal refactor from back when I was working on eth events vote extensions
…/ethbridge/process-proposal-allocator
ProcessProposalBlockSpaceAllocator logic into ProcessProposal
batconjurer
left a comment
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.
nit: Can the tx building fns in prepare proposal be defined in the same order they are used in the main method?
Based on #897
Adds some validation of the
BlockSpaceAllocatorlogic intoProcessProposal.SPECS: https://hackmd.io/unZg8ia4SZCKDQIY-s8d_Q?view=