-
-
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
refactor: revise validator log to output seen instead of exists #5507
Conversation
You may need to update the title to a conventional commit |
Performance Report✔️ no performance regression detected Full benchmark results
|
Just a thought, this log seems a bit verbose as it is printed out per validator. If this is done on startup it might make sense to keep it simple ( The current implementation also does not work correctly as mentioned in #5161 (comment) and #5239 (comment). I think the validator statuses should be printed out each epoch based on clock (data from cache) and not based on fetching Might have to rework this a bit when adding fee recipient and also think about logs for life cycle changes which could be useful for operators This PR addresses some issues but it requires refactoring |
Definitely. I'm all for changes that achieve the same messaging in the most efficient way possible. Did we agree upon including As suggested in #5161 (comment), it would make sense to just do this once on startup to print:
The only time I would foresee this message coming up again is upon re-initialization of the VC or if one of the running validators has a |
Not sure if that was discussed but printing the status on initialization sounds good to me, just need to define how status changes and newly discovered validators should be handled. |
🎉 This PR is included in v1.9.0 🎉 |
Motivation
Referencing feedback from a user on Discord: https://discord.com/channels/593655374469660673/593655641445367808/1108123487840763977
On the
VC
, due to the frequency of this log being output:Validator exists in beacon chain
, there is a probable chance that the wordexists
can be easily misinterpreted with the wordexits
- which should be avoided for bad UX.Description
An alternative syntax for this log output is
Validator seen on beacon chain
which will avoid any misinterpretation.