fix(op-node): Fix Channel Out MaxSize Underflow#5187
Conversation
|
✅ Deploy Preview for opstack-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #5187 +/- ##
===========================================
- Coverage 41.60% 37.58% -4.03%
===========================================
Files 358 216 -142
Lines 22393 18193 -4200
Branches 776 0 -776
===========================================
- Hits 9317 6837 -2480
+ Misses 12368 10686 -1682
+ Partials 708 670 -38
Flags with carried forward coverage won't be shown. Click here to find out more.
|
sebastianst
left a comment
There was a problem hiding this comment.
2 small nits, looks good otherwise ✨
trianglesphere
left a comment
There was a problem hiding this comment.
There's a lot of nice cleanup changes in here, but those are unrelated to primary concern of the PR which is fixing the MaxSizeUnderflow. Those changes should be split out to a new PR.
|
Hey @refcell! This PR has merge conflicts. Please fix them before continuing review. |
sebastianst
left a comment
There was a problem hiding this comment.
Looking good now! Would be nice to still see the remaining tests that got refactored also get a proper test name.
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
Description
Fixes CLI-3649
Context in: #5186. In short, the
maxSizeparameter of the channel out'sOutputFramefunction is unchecked so the23frame overhead size will underflow, resulting in a nearly maxuint64frame size when amaxSizeparameter of < 23 is provided.