-
Notifications
You must be signed in to change notification settings - Fork 86
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
Configurable BlockFetch parameters #2363
Conversation
@@ -145,6 +146,12 @@ data RunNodeArgs blk = RunNodeArgs { | |||
-- | |||
-- Use 'defaultClockSkew' when unsure. | |||
, rnMaxClockSkew :: ClockSkew | |||
|
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 principle I originally had in mind when we introduced RunNodeArgs
is to use these fields for parameters for which we can't pick default values, e.g., NetworkMagic
, ProtocolInfo
, etc. For NodeArgs
and ChainDbArgs
, we can, so we provide functions to customise them without having to force the user (i.e., cardano-node
) to pick the defaults (we know better which defaults to pick).
Over the time RunNodeArgs
has been changed by multiple people and the principle no longer holds. (I want to refactor/clean up this mess at some point).
That's the reason why I prefer a "customise" function instead of requiring concrete values.
Enforce some invariants with `nodeArgsEnforceInvariants`.
bors merge |
No description provided.