-
Notifications
You must be signed in to change notification settings - Fork 5
feat: skipped l1 messages #380
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
Conversation
CodSpeed Performance ReportMerging #380 will not alter performanceComparing Summary
|
frisitano
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.
Added a comment inline.
frisitano
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.
lgtm
| // queue index in descending order. This ensures that we get the latest message | ||
| // included in a block before the provided block number. | ||
| if let Some(record) = models::l1_message::Entity::find() | ||
| .filter(models::l1_message::Column::L2BlockNumber.lt(block_number as i64)) |
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 should consider the case where the last message in a batch skipped and update the L1MessageKey::BlockNumber query to account for it.
Adds a
skippedindex and column on the l1 messages table in order to avoid sequencing skipped L1 messages.