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

Scenario 3 for duplicate block fork choice #34186

Merged
merged 2 commits into from
Nov 21, 2023

Conversation

AshwinSekar
Copy link
Contributor

Problem

Add tree height metric

Summary of Changes

Use tree height metric in fork choice

Fixes #

Copy link

codecov bot commented Nov 21, 2023

Codecov Report

Merging #34186 (e2e7d47) into master (0e6dd54) will increase coverage by 0.0%.
The diff coverage is 99.2%.

Additional details and impacted files
@@           Coverage Diff            @@
##           master   #34186    +/-   ##
========================================
  Coverage    81.9%    81.9%            
========================================
  Files         819      819            
  Lines      219145   219380   +235     
========================================
+ Hits       179529   179741   +212     
- Misses      39616    39639    +23     

@AshwinSekar AshwinSekar merged commit 504f2ee into solana-labs:master Nov 21, 2023
32 checks passed
@AshwinSekar AshwinSekar changed the title Add deepest slot metric Scenario 1 and 3 for duplicate block fork choice Nov 29, 2023
@AshwinSekar AshwinSekar changed the title Scenario 1 and 3 for duplicate block fork choice Scenario 3 for duplicate block fork choice Nov 29, 2023
@AshwinSekar AshwinSekar self-assigned this Nov 29, 2023
@AshwinSekar AshwinSekar added the v1.17 PRs that should be backported to v1.17 label Nov 30, 2023
Copy link
Contributor

mergify bot commented Nov 30, 2023

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 Nov 30, 2023
* reset to deepest slot when last vote is for an invalid fork.

* pr feedback: comments, height starts at 1

(cherry picked from commit 504f2ee)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.17 PRs that should be backported to v1.17
Projects
Development

Successfully merging this pull request may close these issues.

2 participants