-
Notifications
You must be signed in to change notification settings - Fork 748
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
[Merged by Bors] - Fix PERSIST_ETH1_CACHE / PERSIST_OP_POOL Metrics #4278
Conversation
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.
Nice one!
It will be a bit of a race condition to try and read the value before Lighthouse actually shuts down. IIRC we used to persist this cache a bit more regularly.
I guess we can just leave the metric here since it's not doing much harm and it's possible that we get some data from it 🤷
bors r+ |
Do these metrics ever get read? As far as I'm aware, they're only ever updated when lighthouse is shutting down?
Pull request successfully merged into unstable. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page.
|
Do these metrics ever get read? As far as I'm aware, they're only ever updated when lighthouse is shutting down?
Do these metrics ever get read? As far as I'm aware, they're only ever updated when lighthouse is shutting down?
Do these metrics ever get read? As far as I'm aware, they're only ever updated when lighthouse is shutting down?
Do these metrics ever get read? As far as I'm aware, they're only ever updated when lighthouse is shutting down?