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

adds get_proof_offset for Merkle shreds #34798

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

behzadnouri
Copy link
Contributor

Problem

Working towards chained Merkle shreds variant.

Summary of Changes

In preparation of adding chained Merkle shreds variant, the commit reworks api for proof-offset within the shred binary.

In preparation of adding chained Merkle shreds variant, the commit
reworks api for proof-offset within the shred binary.
Copy link

codecov bot commented Jan 16, 2024

Codecov Report

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

Comparison is base (0e90e98) 81.8% compared to head (f8b3a5b) 81.7%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master   #34798     +/-   ##
=========================================
- Coverage    81.8%    81.7%   -0.1%     
=========================================
  Files         825      825             
  Lines      223124   223128      +4     
=========================================
- Hits       182525   182510     -15     
- Misses      40599    40618     +19     

Copy link
Contributor

@gregcusack gregcusack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@behzadnouri behzadnouri merged commit 586c794 into solana-labs:master Jan 17, 2024
35 checks passed
@behzadnouri behzadnouri deleted the self-proof-offset branch January 17, 2024 20:53
@behzadnouri behzadnouri added the v1.18 PRs that should be backported to v1.18 label Feb 4, 2024
Copy link
Contributor

mergify bot commented Feb 4, 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 Feb 4, 2024
In preparation of adding chained Merkle shreds variant, the commit
reworks api for proof-offset within the shred binary.

(cherry picked from commit 586c794)

# Conflicts:
#	ledger/src/shred/merkle.rs
@behzadnouri behzadnouri removed the v1.18 PRs that should be backported to v1.18 label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants