-
Notifications
You must be signed in to change notification settings - Fork 1k
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
beacon node: renaming functions and services to better reflect what they do #14643
base: develop
Are you sure you want to change the base?
Conversation
@@ -240,7 +240,6 @@ func NewService(ctx context.Context, cfg *Config) *Service { | |||
GenesisFetcher: s.cfg.GenesisFetcher, | |||
FinalizationFetcher: s.cfg.FinalizationFetcher, | |||
TimeFetcher: s.cfg.GenesisTimeFetcher, | |||
BlockFetcher: s.cfg.ExecutionChainService, |
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.
We had 2 registrations of Block Fetcher, one as block fetcher and one as Eth1BlockFetcher
@@ -222,7 +222,7 @@ func (s *Service) validateAggregatedAtt(ctx context.Context, signed ethpb.Signed | |||
return s.validateWithBatchVerifier(ctx, "aggregate", set) | |||
} | |||
|
|||
func (s *Service) validateBlockInAttestation(ctx context.Context, satt ethpb.SignedAggregateAttAndProof) bool { | |||
func (s *Service) validateBlockPresenceOrQueueAttestation(ctx context.Context, satt ethpb.SignedAggregateAttAndProof) bool { |
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.
Shorter name + documentation would be better IMO
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.
honestly it feels like there's a deeper issue here why is the save like hacked into this lol the function does 2 things.
couldn't think of a better name, I didn't think validateBlockInAttestation represented what it did
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.
In that case, should we not separate it into two different functions?
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.
I was afraid to do any major changes on this without fully understanding why it was merged in the first place
I would rename |
@@ -222,7 +222,7 @@ func (s *Service) validateAggregatedAtt(ctx context.Context, signed ethpb.Signed | |||
return s.validateWithBatchVerifier(ctx, "aggregate", set) | |||
} | |||
|
|||
func (s *Service) validateBlockInAttestation(ctx context.Context, satt ethpb.SignedAggregateAttAndProof) bool { | |||
func (s *Service) validateBlockPresenceOrQueueAttestation(ctx context.Context, satt ethpb.SignedAggregateAttAndProof) bool { |
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.
In that case, should we not separate it into two different functions?
Co-authored-by: Sammy Rosso <[email protected]>
What type of PR is this?
Other
What does this PR do? Why is it needed?
Which issues(s) does this PR fix?
Fixes #14639
Other notes for review
Acknowledgements