-
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
feat!: delete getTreeNameFromConstructorFn
#287
feat!: delete getTreeNameFromConstructorFn
#287
Conversation
ComputeExtendedDataSquare
to use treeName parametergetTreeNameFromConstructorFn
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #287 +/- ##
==========================================
+ Coverage 80.89% 81.42% +0.52%
==========================================
Files 8 8
Lines 869 845 -24
==========================================
- Hits 703 688 -15
+ Misses 119 113 -6
+ Partials 47 44 -3 ☔ View full report in Codecov by Sentry. |
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.
Looks good, just added a few suggestions.
Ready for re-review. I would like to hold off on merging until after I verify that celestia-app is able to use 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.
LGTM!
This reverts commit 5a03c15.
While attempting to bump celestia-app to the v0.12.0-rc2, I noticed that the `RegisterTree` design leaks an implementation detail to celestia-app: the registering and managing of `treeName`s. Celestia-app has two categories of of trees: 1. erasured namespaced merkle tree in [nmt_wrapper.go](https://github.com/celestiaorg/celestia-app/blob/main/pkg/wrapper/nmt_wrapper.go) 2. EDS subtree root cacher [nmt_caching.go](https://github.com/celestiaorg/celestia-app/blob/main/pkg/inclusion/nmt_caching.go) Each of those categories has trees based on square size and NMT options. Celestia-app needs to be careful to register all the appropriate trees once (and only once) before they are used (via `Compute` or `Import`). I'd like to explore a less breaking option to get celestia-node the original desired feature which was #275. In the meantime, I think we should revert the two big breaking changes so that main can remain release-able. Revert #277 Revert #287 Closes #295 because no longer relevant if we merge this.
While attempting to bump celestia-app to the v0.12.0-rc2, I noticed that the `RegisterTree` design leaks an implementation detail to celestia-app: the registering and managing of `treeName`s. Celestia-app has two categories of of trees: 1. erasured namespaced merkle tree in [nmt_wrapper.go](https://github.com/celestiaorg/celestia-app/blob/main/pkg/wrapper/nmt_wrapper.go) 2. EDS subtree root cacher [nmt_caching.go](https://github.com/celestiaorg/celestia-app/blob/main/pkg/inclusion/nmt_caching.go) Each of those categories has trees based on square size and NMT options. Celestia-app needs to be careful to register all the appropriate trees once (and only once) before they are used (via `Compute` or `Import`). I'd like to explore a less breaking option to get celestia-node the original desired feature which was celestiaorg/rsmt2d#275. In the meantime, I think we should revert the two big breaking changes so that main can remain release-able. Revert celestiaorg/rsmt2d#277 Revert celestiaorg/rsmt2d#287 Closes celestiaorg/rsmt2d#295 because no longer relevant if we merge this.
Closes #286 by deleting
getTreeNameFromConstructorFn
.Closes #288, #289 by fixing those tests.
Inspired by #278
Includes two breaking changes:
ComputeExtendedDataSquare
now accepts a parametertreeName: string
ImportExtendedDataSquare
now accepts a parametertreeName: string