-
Notifications
You must be signed in to change notification settings - Fork 710
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
omni-node: --dev sets manual seal and allows --chain to be set #6646
base: master
Are you sure you want to change the base?
omni-node: --dev sets manual seal and allows --chain to be set #6646
Conversation
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
@@ -128,7 +128,8 @@ pub struct Cli<Config: CliConfig> { | |||
/// | |||
/// This is a dev option, and it won't result in starting or connecting to a parachain network. | |||
/// The resulting node will work on its own, running the wasm blob and artificially producing | |||
/// a block each `dev_block_time` ms, as if it was part of a parachain. | |||
/// a block each `dev_block_time` ms, as if it was part of a parachain. Defaults to 3000ms if | |||
/// not set and `--dev` is used. |
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.
I would be more explicit here about enabling manual sealing and fact that --dev
enables this.
/// Start a dev node that produces a block each `dev_block_time` ms.
///
/// This is a dev option. It enables a manual sealing, meaning blocks are produced manually
/// rather than being part of an actual network consensus process. Using the option won't
/// result in starting or connecting to a parachain network. The resulting node will work on
/// its own, running the wasm blob and artificially producing a block each `dev_block_time` ms,
/// as if it was part of a parachain.
///
/// The `--dev` flag sets the `dev_block_time` to a default value of 3000ms unless explicitly provided.
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.
Used your phrasing here: d6faae7
#[arg(long, conflicts_with_all = &["chain"])] | ||
/// This flag sets `--chain=dev`, `--force-authoring`, `--rpc-cors=all`, `--alice`, and `--tmp` | ||
/// flags, unless explicitly overridden. It also disables local peer discovery (see `--no-mdns` | ||
/// and `--discover-local`). |
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.
Should we mention manual seal here? (I know it does not enable it for every node, but I think it would be good to have this information in cli).
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.
Added a note here: d6faae7.
Signed-off-by: Iulian Barbu <[email protected]>
Co-authored-by: Michal Kucharczyk <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Description
This PR changes a few things:
--dev
flag will not conflict with--chain
anymore, but if--chain
is not given will set--chain=dev
.--dev-block-time
is optional and it defaults to 3000ms if not set after setting--dev
.--dev
.Closes: #6537
Integration
Relevant for node/runtime developers that use OmniNode lib, including
polkadot-omni-node
binary, although the recommended way for runtime development is to usechopsticks
.Review Notes
parachain-template-node
as is (meaning--dev
isn't usable and testing a runtime with theparachain-template-node
still needs a relay chain here). I am doing this because I think we want either way to phase outparachain-template-node
and adding manual seal support for it is wasted effort. We might add support though if the demand is forparachain-template-node
.--dev-block-time
. Also, would want first to align & merge on runtime metadata checks we added in Omni Node here: omni-node: add metadata checks for runtime/parachain compatibility #6450 before starting to infer AURA config slot duration via the same way.--dev
now.