-
-
Notifications
You must be signed in to change notification settings - Fork 434
refactor: query ShufflingCache for shuffling data #8743
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
Conversation
Summary of ChangesHello @twoeths, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly refactors the handling of beacon committee and attestation data queries. It centralizes the underlying logic into a new Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request is a significant refactoring to query shuffling data from ShufflingCache instead of EpochCache. The changes are spread across multiple packages and appear to be well-implemented, aligning with the goal of migrating away from EpochCache methods. I've included a couple of suggestions to enhance code quality: one to address code duplication by introducing a helper method, and another to correct a minor typo in an error code for better consistency. Overall, the changes look good.
Performance Report✔️ no performance regression detected Full benchmark results
|
0704cbd to
ceaf192
Compare
…onCommittee(s) in shufflingUtils.ts
336e6b9 to
903153a
Compare
|
found a good fix to populate |
nflaig
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good overall, just a few nits
packages/beacon-node/test/perf/chain/opPools/aggregatedAttestationPool.test.ts
Outdated
Show resolved
Hide resolved
| }); | ||
|
|
||
| // in forky condition, make sure to populate ShufflingCache with regened state | ||
| // otherwise it's failed to get indexed attestations from shuffling cache later |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did this always happen or just in certain edge cases?
| // otherwise it's failed to get indexed attestations from shuffling cache later | |
| // otherwise it may fail to get indexed attestations from shuffling cache later |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it happens on super forky condition, specifically in fork_choice spec_tests
ShufflingCache is designed to store only 4 epochs, say epoch 4, 5, 6, 7, then it reorg to epoch 3, then we cannot use ShufflingCache to get indexed attestations of below call (because Shufflings of epoch 3 was removed)
to make it safe we can just process regened states right after getPreState call (there are 2 of them)
that was the scenario in #8743 (comment)
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request refactors the codebase to replace direct calls to EpochCache methods with calls to the ShufflingCache for retrieving shuffling data. This change is motivated by the migration to native state-transition, which eliminates the ability to query EpochCache methods directly. The changes involve modifying several files to use the ShufflingCache for methods like getIndexedAttestation(), getAttestingIndices(), getBeaconCommittee(), and getBeaconCommittees().
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## unstable #8743 +/- ##
============================================
+ Coverage 52.11% 52.13% +0.01%
============================================
Files 848 848
Lines 64252 64178 -74
Branches 4735 4730 -5
============================================
- Hits 33488 33457 -31
+ Misses 30695 30652 -43
Partials 69 69 🚀 New features to boost your workflow:
|
Motivation
Description
Closes #8655
blocked by #8721