-
-
Notifications
You must be signed in to change notification settings - Fork 291
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
Submit unaggregated attestations in one go #3923
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3923 +/- ##
==========================================
+ Coverage 36.32% 36.48% +0.15%
==========================================
Files 324 324
Lines 9059 9091 +32
Branches 1453 1470 +17
==========================================
+ Hits 3291 3317 +26
- Misses 5597 5600 +3
- Partials 171 174 +3 |
Performance Report✔️ no performance regression detected Full benchmark results
|
await sleep(this.clock.msToSlot(slot + 2 / 3), signal); | ||
this.metrics?.attesterStepCallProduceAggregate.observe(this.clock.secFromSlot(slot + 2 / 3)); | ||
|
||
const dutiesByCommitteeIndex = groupAttDutiesByCommitteeIndex(this.dutiesService.getDutiesAtSlot(slot)); |
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.
@tuyennhv why do we need to call this.dutiesService.getDutiesAtSlot
again here? I would assume we could just do
const dutiesByCommitteeIndex = groupAttDutiesByCommitteeIndex(duties);
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.
yes we can just use duties
there, no need to call that again
Motivation
There are a lot of same logs like below in hetzner nodes:
Description
Before
After
part of #3922