-
Notifications
You must be signed in to change notification settings - Fork 476
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
dynamic-lambda: continue tracking the best proposal even after freezing #5701
Conversation
…specific to the msgp decoder
remove commented out code from when we were trying to get receivedAt for proposal-votes
fix comment to say validated instead of received
Co-authored-by: Jason Paulos <[email protected]>
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.
The updated naming conventions made this noticeably easier to read/follow. There is a codegen failure to address on the build.
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.
LGTM -- it appears the build error is because msgp generation needs to be run again
Summary
This PR builds on #5654 and changes the credential propagation and tracking strategy, so we continue propagating credentials for some time after the round concluded and continue to track when we received the lowest credential. This makes the measurements for the dynamic lambda feature independent of the actual filter timeout being set.
Test Plan
Extending existing tests to make sure that better period 0 step 0 credentials get propagated even if they're late.
Extending existing tests to make sure that better period 0 step 0 credentials impact the measurements used in setting the filter timeout.