-
Notifications
You must be signed in to change notification settings - Fork 38
[Peras 7] Introduce and propagate feature flags down to NodeKernelArgs #1780
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
base: main
Are you sure you want to change the base?
Conversation
|
Please note that To provide some confidence about the future integration into |
d94732b to
8878cb1
Compare
Brings in cardano-base and propagates a set of `CardanoFeatureFlag`s from the top-level `RunNodeArgs` down to the `NodeKernelArgs`. This is currently needed by upcoming PRs that need to conditionally enable certain behavior based on the `PerasFlag` feature flag.
8878cb1 to
32dbee3
Compare
jasagredo
left a comment
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.
This looks correct to me.
#1780) This PR brings in `cardano-base` and propagates a set of `CardanoFeatureFlag`s from the top-level `RunNodeArgs` down to the `NodeKernelArgs`. This is currently needed by upcoming PRs that need to conditionally enable certain behavior based on the `PerasFlag` feature flag (e.g, spawning voting and object diffusion threads, deciding when a node can consider itself as CaughtUp, etc.).
#1780) This PR brings in `cardano-base` and propagates a set of `CardanoFeatureFlag`s from the top-level `RunNodeArgs` down to the `NodeKernelArgs`. This is currently needed by upcoming PRs that need to conditionally enable certain behavior based on the `PerasFlag` feature flag (e.g, spawning voting and object diffusion threads, deciding when a node can consider itself as CaughtUp, etc.).
This PR brings in
cardano-baseand propagates a set ofCardanoFeatureFlags from the top-levelRunNodeArgsdown to theNodeKernelArgs.This is currently needed by upcoming PRs that need to conditionally enable certain behavior based on the
PerasFlagfeature flag (e.g, spawning voting and object diffusion threads, deciding when a node can consider itself as CaughtUp, etc.).