8000 v2.2: include existing zero lamport in duplicates (backport of #6158) by mergify[bot] · Pull Request #6160 · anza-xyz/agave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

v2.2: include existing zero lamport in duplicates (backport of #6158) #6160

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

Merged
merged 1 commit into from
May 8, 2025

Conversation

mergify[bot]
Copy link
@mergify mergify bot commented May 8, 2025

Problem

Include exising zero accounts in duplicates list so that lthash get the correct set of accounts to mixout when verifying at startup.

Summary of Changes

Fixes #6153


This is an automatic backport of pull request #6158 done by [Mergify](https://mergify.com).

@mergify mergify bot requested a review from a team as a code owner May 8, 2025 18:14
Copy link
@jeffwashington jeffwashington left a comment

Choose a reason for hiding this comment

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

lgtm

@codecov-commenter
8000 Copy link

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 83.4%. Comparing base (97eace4) to head (4d54804).
Report is 1 commits behind head on v2.2.

Additional details and impacted files
@@           Coverage Diff           @@
##             v2.2    #6160   +/-   ##
=======================================
  Coverage    83.4%    83.4%           
=======================================
  Files         806      806           
  Lines      373245   373245           
=======================================
+ Hits       311361   311379   +18     
+ Misses      61884    61866   -18     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

InsertNewEntryResults::ExistedNewEntryZeroLamports => {}
InsertNewEntryResults::ExistedNewEntryNonZeroLamports(other_slot) => {
InsertNewEntryResults::ExistedNewEntryZeroLamports(other_slot)
| InsertNewEntryResults::ExistedNewEntryNonZeroLamports(other_slot) => {
Copy link

Choose a reason for hiding this comment

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

Do these need to be differentiated anymore?

Copy link

Choose a reason for hiding this comment

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

Looks like ExistedNewEntryZeroLamports vs ExistedNewEntryNonZeroLamports are handled identically in all uses now, aren't they?

Copy link

Choose a reason for hiding this comment

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

Yes, they are.
We can refactor them in master with a future PR. For a backport PR, we would like to exclude refactoring changes.

Copy link

Choose a reason for hiding this comment

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

Sounds good.

@HaoranYi HaoranYi merged commit 80eb5fc into v2.2 May 8, 2025
46 checks passed
@HaoranYi HaoranYi deleted the mergify/bp/v2.2/pr-6158 branch May 8, 2025 20:09
nibty pushed a commit to x1-labs/tachyon that referenced this pull request Jun 11, 2025
…yz#6158) (anza-xyz#6160)

include existing zero lamport in duplicates (anza-xyz#6158)

(cherry picked from commit a1f90ac)

Co-authored-by: HaoranYi <219428+HaoranYi@users.noreply.github.com>
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.

6 participants
0