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

rolls out chained Merkle shreds to ~5% of mainnet slots #4019

Merged

Conversation

behzadnouri
Copy link

Problem

Rolling out chained Merkle shreds to testnet.

Summary of Changes

The commit rolls out chained Merkle shreds to ~5% of mainnet slots.

@behzadnouri behzadnouri force-pushed the chained-merkle-shreds-rollout branch from 2b661b3 to 9098f79 Compare December 10, 2024 01:10
@behzadnouri behzadnouri merged commit d3fe8f8 into anza-xyz:master Dec 15, 2024
40 checks passed
@behzadnouri behzadnouri deleted the chained-merkle-shreds-rollout branch December 15, 2024 23:58
@behzadnouri behzadnouri added v2.0 Backport to v2.0 branch v2.1 Backport to v2.1 branch labels Dec 15, 2024
Copy link

mergify bot commented Dec 15, 2024

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

Copy link

mergify bot commented Dec 15, 2024

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

mergify bot pushed a commit that referenced this pull request Dec 16, 2024
mergify bot pushed a commit that referenced this pull request Dec 16, 2024
(cherry picked from commit d3fe8f8)

# Conflicts:
#	turbine/src/broadcast_stage/standard_broadcast_run.rs
behzadnouri added a commit that referenced this pull request Dec 16, 2024
behzadnouri added a commit that referenced this pull request Dec 16, 2024
(cherry picked from commit d3fe8f8)

# Conflicts:
#	turbine/src/broadcast_stage/standard_broadcast_run.rs
mergify bot added a commit that referenced this pull request Dec 17, 2024
…rt of #4019) (#4130)

rolls out chained Merkle shreds to ~5% of mainnet slots (#4019)

(cherry picked from commit d3fe8f8)

Co-authored-by: behzad nouri <behzadnouri@gmail.com>
behzadnouri added a commit that referenced this pull request Dec 18, 2024
…rt of #4019) (#4131)

* rolls out chained Merkle shreds to ~5% of mainnet slots (#4019)

(cherry picked from commit d3fe8f8)

# Conflicts:
#	turbine/src/broadcast_stage/standard_broadcast_run.rs

* resolves merge conflicts

---------

Co-authored-by: behzad nouri <behzadnouri@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2.0 Backport to v2.0 branch v2.1 Backport to v2.1 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants