op-node: handle when L1 time gap is larger than sequencer time drift#4809
op-node: handle when L1 time gap is larger than sequencer time drift#4809
Conversation
|
|
Adding a comment at optimism/op-node/rollup/derive/batch_queue.go Line 236 in b1f2812 |
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
b1f2812 to
92d06e0
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #4809 +/- ##
===========================================
- Coverage 40.44% 35.83% -4.61%
===========================================
Files 323 183 -140
Lines 19549 15475 -4074
Branches 761 0 -761
===========================================
- Hits 7906 5546 -2360
+ Misses 11034 9359 -1675
+ Partials 609 570 -39
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
Rebasing this now, to ensure it runs on top of latest derivation changes |
92d06e0 to
634dd94
Compare
|
will rebase to fix the lint timeout issue |
634dd94 to
48a8024
Compare
mslipper
left a comment
There was a problem hiding this comment.
LGTM. Proto walked me through this live, and we reviewed together.
Description
Subset of original #4758.
Handle rare case when L1 block time gap is larger than the sequencer time drift to not halt safe head.
Tests
See new unit tests to cover new sequencer time drift handling.
Invariants
L2 time >= L1 origin timeat all timesAdditional context
See design doc.
Fix CLI-3354