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

patches slots_per_epoch vs last_slot ordering in shred_fetch_stage #34338

Merged
merged 1 commit into from
Dec 6, 2023

Conversation

behzadnouri
Copy link
Contributor

Problem

Orders are wrong and assigned wrong values.

Summary of Changes

Fixed ordering.

@behzadnouri behzadnouri marked this pull request as ready for review December 6, 2023 14:01
@behzadnouri behzadnouri added v1.16 PRs that should be backported to v1.16 v1.17 PRs that should be backported to v1.17 labels Dec 6, 2023
Copy link
Contributor

mergify bot commented Dec 6, 2023

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.

Copy link
Contributor

mergify bot commented Dec 6, 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.

Copy link

codecov bot commented Dec 6, 2023

Codecov Report

Merging #34338 (af80933) into master (fa25176) will decrease coverage by 0.1%.
The diff coverage is 100.0%.

Additional details and impacted files
@@            Coverage Diff            @@
##           master   #34338     +/-   ##
=========================================
- Coverage    81.9%    81.9%   -0.1%     
=========================================
  Files         819      819             
  Lines      220422   220422             
=========================================
- Hits       180673   180672      -1     
- Misses      39749    39750      +1     

Copy link
Contributor

@AshwinSekar AshwinSekar left a comment

Choose a reason for hiding this comment

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

it seems we were getting by before because we set these correctly after DEFAULT_MS_PER_SLOT later in the loop?

@behzadnouri
Copy link
Contributor Author

it seems we were getting by before because we set these correctly after DEFAULT_MS_PER_SLOT later in the loop?

yeah, i guess so

@behzadnouri behzadnouri merged commit b1c701e into solana-labs:master Dec 6, 2023
35 checks passed
mergify bot pushed a commit that referenced this pull request Dec 6, 2023
mergify bot pushed a commit that referenced this pull request Dec 6, 2023
@behzadnouri behzadnouri deleted the patch-last-slots branch December 6, 2023 20:50
behzadnouri added a commit that referenced this pull request Dec 6, 2023
…tage (backport of #34338) (#34345)

patches slots_per_epoch vs last_slot ordering in shred_fetch_stage (#34338)

(cherry picked from commit b1c701e)

Co-authored-by: behzad nouri <behzadnouri@gmail.com>
behzadnouri added a commit that referenced this pull request Dec 6, 2023
…tage (backport of #34338) (#34344)

patches slots_per_epoch vs last_slot ordering in shred_fetch_stage (#34338)

(cherry picked from commit b1c701e)

Co-authored-by: behzad nouri <behzadnouri@gmail.com>
@steviez
Copy link
Contributor

steviez commented Dec 12, 2023

it seems we were getting by before because we set these correctly after DEFAULT_MS_PER_SLOT later in the loop?

yeah, i guess so

Late to the party, but agreed with Behzad; the initial values were bad but after 400ms they would be corrected. Good cleanup anyways and thanks for catching this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.16 PRs that should be backported to v1.16 v1.17 PRs that should be backported to v1.17
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants