-
Notifications
You must be signed in to change notification settings - Fork 969
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(blob/service): fix handling of the padding shares #3404
Conversation
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.
The fix LGTM. Only have two blocking on the test file and need to make an issue.
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.
Lets make test, that generates edses with multiple conditions of padding shares instead of using eds.json. 1 padding share, multiple padding shares between blobs, multiple padding shares between namespaces. It will help to add more cases in future too.
e6ae531
to
8b3a48d
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3404 +/- ##
==========================================
- Coverage 44.83% 44.53% -0.30%
==========================================
Files 265 272 +7
Lines 14620 15282 +662
==========================================
+ Hits 6555 6806 +251
- Misses 7313 7692 +379
- Partials 752 784 +32 ☔ View full report in Codecov by Sentry. |
8b3a48d
to
309c91b
Compare
@renaynay, I propose to make a new patch for this fix, instead of 0.14.0 as its blocking Astria and in general a critical bug. |
Fixes the issue with the missing blob. Initially, there was an incorrect assumption that only one padding share is possible between two blobs. So, the Blob service was skipping only one share instead of multiple. * Fixed parsing logic allowing to skip multiple padding shares; * Added a test case that retrieves the EDS and finds the correct number of blobs;
Fixes the issue with the missing blob. Initially, there was an incorrect assumption that only one padding share is possible between two blobs. So, the Blob service was skipping only one share instead of multiple.