-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
enables merkle shreds for devnet and development clusters #32533
Conversation
99639ce
to
567d1ea
Compare
Codecov Report
@@ Coverage Diff @@
## master #32533 +/- ##
=======================================
Coverage 82.0% 82.0%
=======================================
Files 780 780
Lines 210721 210723 +2
=======================================
+ Hits 172852 172874 +22
+ Misses 37869 37849 -20 |
567d1ea
to
2e79ba9
Compare
2e79ba9
to
4cfc161
Compare
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!
At a minimum, I think we should backport the change to keep testnet using merkle all the time to v1.16; don't want to accidentally turn those off. Not clear to me if we should BP the change for devnet and development clusters to v1.16 as well
I think BP changes for |
automerge label removed due to a CI failure |
(cherry picked from commit 7f2f013)
…kport of #32533) (#32552) enables merkle shreds for devnet and development clusters (#32533) (cherry picked from commit 7f2f013) Co-authored-by: behzad nouri <[email protected]>
Problem
Switching from Legacy to Merkle shreds.
Summary of Changes
Enable Merkle shreds for devnet and development clusters.