Skip to content
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

v1.18: adds feature to enable chained Merkle shreds (backport of #34916) #35083

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 5, 2024

This is an automatic backport of pull request #34916 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

During a cluster upgrade when only half of the cluster can ingest the new shred
variant, sending shreds of the new variant can cause nodes to diverge.
The commit adds a feature to enable chained Merkle shreds explicitly.

(cherry picked from commit d4fdcd9)
Copy link

codecov bot commented Feb 5, 2024

Codecov Report

Attention: 37 lines in your changes are missing coverage. Please review.

Comparison is base (0a99e95) 81.6% compared to head (b39e6c1) 81.6%.

Additional details and impacted files
@@            Coverage Diff            @@
##            v1.18   #35083     +/-   ##
=========================================
- Coverage    81.6%    81.6%   -0.1%     
=========================================
  Files         828      828             
  Lines      224065   224100     +35     
=========================================
- Hits       182966   182926     -40     
- Misses      41099    41174     +75     

@behzadnouri behzadnouri added the automerge Merge this Pull Request automatically once CI passes label Feb 5, 2024
@mergify mergify bot merged commit 5ca66a3 into v1.18 Feb 5, 2024
37 checks passed
@mergify mergify bot deleted the mergify/bp/v1.18/pr-34916 branch February 5, 2024 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this Pull Request automatically once CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants