Skip to content

core: Adjust vote-storage handling#9898

Merged
steviez merged 3 commits intoanza-xyz:masterfrom
steviez:vote_storage
Jan 10, 2026
Merged

core: Adjust vote-storage handling#9898
steviez merged 3 commits intoanza-xyz:masterfrom
steviez:vote_storage

Conversation

@steviez
Copy link

@steviez steviez commented Jan 10, 2026

Summary of Changes

Our previous checks were a little lax; let's plug in some robust checks

@codecov-commenter
Copy link

Codecov Report

❌ Patch coverage is 94.28571% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.6%. Comparing base (ce7a7cb) to head (a00fa2a).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #9898   +/-   ##
=======================================
  Coverage    82.6%    82.6%           
=======================================
  Files         848      848           
  Lines      316763   316771    +8     
=======================================
+ Hits       261754   261810   +56     
+ Misses      55009    54961   -48     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@steviez steviez marked this pull request as ready for review January 10, 2026 04:20
@steviez steviez added this pull request to the merge queue Jan 10, 2026
@t-nelson t-nelson added v3.0 Backport to v3.0 branch v3.1 Backport to v3.1 branch labels Jan 10, 2026
@mergify
Copy link

mergify bot commented Jan 10, 2026

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.

@mergify
Copy link

mergify bot commented Jan 10, 2026

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.

Merged via the queue into anza-xyz:master with commit 8cebdeb Jan 10, 2026
49 checks passed
@steviez steviez deleted the vote_storage branch January 10, 2026 04:33
mergify bot pushed a commit that referenced this pull request Jan 10, 2026
* filter unauthorized votes

* check authorized voter has signed

* fix failing test

---------

Co-authored-by: OliverNChalk <[email protected]>
(cherry picked from commit 8cebdeb)

# Conflicts:
#	core/src/banking_stage/latest_validator_vote_packet.rs
#	core/src/banking_stage/vote_storage.rs
mergify bot pushed a commit that referenced this pull request Jan 10, 2026
* filter unauthorized votes

* check authorized voter has signed

* fix failing test

---------

Co-authored-by: OliverNChalk <[email protected]>
(cherry picked from commit 8cebdeb)
steviez added a commit that referenced this pull request Jan 10, 2026
core: Adjust vote-storage handling (#9898)

(cherry picked from commit 8cebdeb)

Co-authored-by: steviez <[email protected]>
Co-authored-by: OliverNChalk <[email protected]>
steviez added a commit that referenced this pull request Jan 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v3.0 Backport to v3.0 branch v3.1 Backport to v3.1 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants