Handle duplicate block submission - #1471
Conversation
|
Warning Rate Limit Exceeded@Manav-Aggarwal has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 48 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. WalkthroughThe recent updates involve enhancing the Changes
Assessment against linked issues
Related issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1471 +/- ##
==========================================
+ Coverage 50.23% 51.27% +1.04%
==========================================
Files 52 52
Lines 6762 6726 -36
==========================================
+ Hits 3397 3449 +52
+ Misses 3024 2929 -95
- Partials 341 348 +7 ☔ View full report in Codecov by Sentry. |
6982ed6 to
e93dfe3
Compare
MSevey
left a comment
There was a problem hiding this comment.
This needs an update to testing.
Test cases I can thinking of that we should understand how they execute.
Assuming starting with Blocks a b c
- happy case, all are submitted on first round
- a and b are submitted first because including c triggers size limit. C is then submitted on second round.
- C is too big on it's own, never submitted but a and b are
- C has a marshal issue. A and b should still be submitted ( I think this case currently isn't possible with the code based on
SubmitBlocks) - A is too big on its own
- A has a marshal issue
for cases 5 and 6, what should be the desired outcome? Do we never submit any blocks if the current next block is bad? Based on SubmitBlocks that appears to be the case.
38c330c to
bd78dbd
Compare
There was a problem hiding this comment.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (2)
- block/manager.go (1 hunks)
- block/manager_test.go (1 hunks)
Files skipped from review as they are similar to previous changes (2)
- block/manager.go
- block/manager_test.go
bd78dbd to
b6a2808
Compare
bb3185a to
e489f68
Compare
Added test cases for 1, 2, 3. Follow up issue for the rest: #1530 |
Co-authored-by: Matthew Sevey <mjsevey@gmail.com>
fded548 to
dc532a8
Compare
There was a problem hiding this comment.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (2)
- block/manager.go (1 hunks)
- block/manager_test.go (2 hunks)
Files skipped from review as they are similar to previous changes (2)
- block/manager.go
- block/manager_test.go
|
should we also optimize this to as there is not much difference and lot of duplicate code. |
This was introduced in https://github.com/rollkit/rollkit/pull/1466/files. I think we can optimize. |
tzdybal
left a comment
There was a problem hiding this comment.
LGTM. This is even better than mock.
Overview
Closes: #1472
Checklist
Summary by CodeRabbit