Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

v1.16: revises turbine epoch stakes for shreds propagation (backport of #32743) #33041

Merged
merged 1 commit into from
Aug 29, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 28, 2023

This is an automatic backport of pull request #32743 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

Bank::get_leader_schedule_epoch returns: 1 + EpochSchedule::get_epoch.
As a result, at the epoch boundaries when the propagated shred is from
the next epoch, we are looking for epoch stakes for 2 epochs ahead of
the root or working bank's epoch.
However, the bank structure only contains epoch stakes for one epoch
ahead. This results in shreds propagated at epoch boundary having
unknown epoch stakes.

(cherry picked from commit d5c2dac)
@codecov
Copy link

codecov bot commented Aug 28, 2023

Codecov Report

Merging #33041 (f156233) into v1.16 (cb8cb45) will increase coverage by 0.0%.
The diff coverage is 77.7%.

@@           Coverage Diff           @@
##            v1.16   #33041   +/-   ##
=======================================
  Coverage    81.9%    81.9%           
=======================================
  Files         762      762           
  Lines      208172   208179    +7     
=======================================
+ Hits       170669   170701   +32     
+ Misses      37503    37478   -25     

@behzadnouri
Copy link
Contributor

Need to backport this because this is damaging shreds propagation right at epoch boundary which we already have a lot of problems.
The change is behind a feature-gate, and by itself is a no-op until the feature is activated.

@behzadnouri behzadnouri added the automerge Merge this Pull Request automatically once CI passes label Aug 29, 2023
@mergify mergify bot merged commit da98ea2 into v1.16 Aug 29, 2023
@mergify mergify bot deleted the mergify/bp/v1.16/pr-32743 branch August 29, 2023 01:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
automerge Merge this Pull Request automatically once CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants