This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Add a build-sync-spec
subcommand and remove the CHT roots from the light sync state.
#6999
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4616e77
Move subcommands from sc-cli to nodes
expenses b1df214
Merge remote-tracking branch 'origin/master' into ashley-remove-subco…
expenses 101a439
Add --build-sync-spec subcommand
expenses 2b7fd85
Remove CHTs from snapshots
expenses 83c0c2a
Merge remote-tracking branch 'origin/master' into ashley-chain-spec-s…
expenses ca61ff2
Keep ProvideChtRoots
expenses File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,113 @@ | ||
// This file is part of Substrate. | ||
|
||
// Copyright (C) 2018-2020 Parity Technologies (UK) Ltd. | ||
// SPDX-License-Identifier: GPL-3.0-or-later WITH Classpath-exception-2.0 | ||
|
||
// This program is free software: you can redistribute it and/or modify | ||
// it under the terms of the GNU General Public License as published by | ||
// the Free Software Foundation, either version 3 of the License, or | ||
// (at your option) any later version. | ||
|
||
// This program is distributed in the hope that it will be useful, | ||
// but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | ||
// GNU General Public License for more details. | ||
|
||
// You should have received a copy of the GNU General Public License | ||
// along with this program. If not, see <https://www.gnu.org/licenses/>. | ||
|
||
use crate::error; | ||
use crate::params::{SharedParams, NetworkParams}; | ||
use crate::CliConfiguration; | ||
use log::info; | ||
use sc_network::config::build_multiaddr; | ||
use sc_service::{config::{MultiaddrWithPeerId, NetworkConfiguration}, ChainSpec}; | ||
use structopt::StructOpt; | ||
use std::io::Write; | ||
use std::sync::Arc; | ||
use sp_runtime::traits::Block as BlockT; | ||
use sc_service::chain_ops::build_light_sync_state; | ||
use sc_service::NetworkStatusSinks; | ||
use futures::{FutureExt, StreamExt}; | ||
use futures::future::ready; | ||
|
||
/// The `build-sync-spec` command used to build a chain spec that contains a light client state | ||
/// so that light clients can sync faster. | ||
#[derive(Debug, StructOpt)] | ||
pub struct BuildSyncSpecCmd { | ||
/// Force raw genesis storage output. | ||
#[structopt(long = "raw")] | ||
pub raw: bool, | ||
|
||
/// Sync the chain using a full client first. | ||
#[structopt(long)] | ||
pub sync_first: bool, | ||
|
||
/// Disable adding the default bootnode to the specification. | ||
/// | ||
/// By default the `/ip4/127.0.0.1/tcp/30333/p2p/NODE_PEER_ID` bootnode is added to the | ||
/// specification when no bootnode exists. | ||
#[structopt(long = "disable-default-bootnode")] | ||
pub disable_default_bootnode: bool, | ||
|
||
#[allow(missing_docs)] | ||
#[structopt(flatten)] | ||
pub shared_params: SharedParams, | ||
|
||
#[allow(missing_docs)] | ||
#[structopt(flatten)] | ||
pub network_params: NetworkParams, | ||
} | ||
|
||
impl BuildSyncSpecCmd { | ||
/// Run the build-sync-spec command | ||
pub async fn run<B, CL>( | ||
&self, | ||
mut spec: Box<dyn ChainSpec>, | ||
network_config: NetworkConfiguration, | ||
client: Arc<CL>, | ||
network_status_sinks: NetworkStatusSinks<B>, | ||
) -> error::Result<()> | ||
where | ||
B: BlockT, | ||
CL: sp_blockchain::HeaderBackend<B>, | ||
{ | ||
if self.sync_first { | ||
network_status_sinks.network_status(std::time::Duration::from_secs(1)).filter(|(status, _)| { | ||
ready(status.sync_state == sc_network::SyncState::Idle && status.num_sync_peers > 0) | ||
}).into_future().map(drop).await; | ||
} | ||
|
||
let light_sync_state = build_light_sync_state(client)?; | ||
spec.set_light_sync_state(light_sync_state.to_serializable()); | ||
|
||
info!("Building chain spec"); | ||
let raw_output = self.raw; | ||
|
||
if spec.boot_nodes().is_empty() && !self.disable_default_bootnode { | ||
let keys = network_config.node_key.into_keypair()?; | ||
let peer_id = keys.public().into_peer_id(); | ||
let addr = MultiaddrWithPeerId { | ||
multiaddr: build_multiaddr![Ip4([127, 0, 0, 1]), Tcp(30333u16)], | ||
peer_id, | ||
}; | ||
spec.add_boot_node(addr) | ||
} | ||
|
||
let json = sc_service::chain_ops::build_spec(&*spec, raw_output)?; | ||
if std::io::stdout().write_all(json.as_bytes()).is_err() { | ||
let _ = std::io::stderr().write_all(b"Error writing to stdout\n"); | ||
} | ||
Ok(()) | ||
} | ||
} | ||
|
||
impl CliConfiguration for BuildSyncSpecCmd { | ||
fn shared_params(&self) -> &SharedParams { | ||
&self.shared_params | ||
} | ||
|
||
fn network_params(&self) -> Option<&NetworkParams> { | ||
Some(&self.network_params) | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 wonder why this build_spec is in
chain_ops/import_blocks.rs
, maybe it should go to its own file like the other operations. Or maybe it shouldn't go there at all because it's not really an operation on the blockchain but on the spec. Or maybe it shouldn't even exist, it's not like it's doing much at all:spec.as_json(raw).map_err(Into::into)
.