-
Notifications
You must be signed in to change notification settings - Fork 47
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(block_production): continue pending block now reexecutes the previous transactions #411
Conversation
…ious transactions
note: the file change count is 45 which seems like a lot, but most files have a 1-line change. I don't believe this is a large PR |
/// Get class info + sierra compiled when it's a sierra class. | ||
// Note/TODO: "ConvertedClass" is the name of the type that has info + sierra compiled, and it is used for blockifier | ||
// convertion & storage. We should rename it, as this feels like undecipherable madara-specific jargon at this point. |
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.
We could rename it to ResolvedClass
or CanonicalClass
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.
why canonical?
@@ -26,53 +26,26 @@ pub enum Error { | |||
/// | |||
/// **note:** this function does not support deploy transaction | |||
/// because it is not supported by blockifier | |||
pub fn to_blockifier_transactions( | |||
pub fn to_blockifier_transaction( |
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.
👍
Pull Request type
What is the current behavior?
We had a hacky way of continuing the pending block state on restart.
What is the new behavior?
Now, we re-add all the transactions from the pending block into the mempool when restarting with a priority.
I also did some refactoring here and there:
Does this introduce a breaking change?
No, db remains unchanged.