-
Notifications
You must be signed in to change notification settings - Fork 33
PohService needs to set use_alpenglow_tick_producer flag on startup
#59
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
Conversation
| if !poh_exit.load(Ordering::Relaxed) | ||
| // Should be set by replay_stage after it sees a notarized | ||
| // block in the new alpenglow epoch | ||
| && poh_recorder.read().unwrap().is_alpenglow_enabled |
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.
Do you still need this test? Maybe just say the only way it exits the previous loop is either:
- poh_exit is true
- alpenglow is enabled
So only exit the loop if 1 is true.
Then you can move the info loop to line 169~175?
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 info log is only necessary if we started in not alpenglow mode, and then migrated to alpenglow. If we started in alpenglow mode, there's no need to print that we're migrating
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.
Hmm ok, we can also do:
if poh_exit.load(Ordering::Relaxed) {
return;
} else { // must exit because of Alpenglow
info(...)
}
Your choice.
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.
updated!
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.
hmm actually I might like the original better, I want to explicitly check that alpenglow was enabled in case somebody else adds another path/error on which poh would exit
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.
Ok, that's fair.
| if !poh_exit.load(Ordering::Relaxed) | ||
| // Should be set by replay_stage after it sees a notarized | ||
| // block in the new alpenglow epoch | ||
| && poh_recorder.read().unwrap().is_alpenglow_enabled |
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.
Ok, that's fair.
PohService needs to set `use_alpenglow_tick_producer` flag on startup (#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
PohService needs to set `use_alpenglow_tick_producer` flag on startup (anza-xyz#59)
Problem
flag
use_alpenglow_tick_produceris not enabled at startupSummary of Changes
Fixes #