-
Notifications
You must be signed in to change notification settings - Fork 80
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: deepcopy filliing nil data with zeroes #310
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #310 +/- ##
==========================================
+ Coverage 80.89% 82.30% +1.40%
==========================================
Files 8 7 -1
Lines 869 616 -253
==========================================
- Hits 703 507 -196
+ Misses 119 66 -53
+ Partials 47 43 -4 ☔ View full report in Codecov by Sentry. |
The rust mind cannot comprehend this 😂 |
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.
Minor correction: The bug was there before the linked PR. The PR extracted existing code as is.
I wish golang had immutables too 🤝 |
…struction (#3306) We should not restrict the BEFP constructor to collect proof only for orthogonal axes to ErrByzantine. This PR enables the constructor to attempt building both Row and Col proofs, irrespective of the ErrByzantine axis type. Additionally, it prevents the BEFP constructor from requesting proofs pr shars from the network by granting access exclusively to the local blockstore. There should be sufficient proofs and shares in the local blockstore at the time BEFP is detected. Breaks befp message, by introducing proofAxis field, which is not supported by older befp subscribers. Depends on - #3305 to have enough data in blockstore. - celestiaorg/rsmt2d#310 to provide proper coordinates of verified shares
Corrects the bug introduced by #100. Currently, if
deepcopy()
encounters nil inner slice values, it creates a slice of 0 length, which is incorrect. This PR addresses the issue. The problem becomes evident when eds is partially computed, resulting in Row() or Col() methods returning invalid copies.On the side note, it is technically breaking public API change. But the nature of the bug suggests noone relied on existing misbehaviour before.