Fix bug in spawn_running_signer which was incorrectly using node rather than endpoint

Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
This commit is contained in:
Jacinta Ferrant
2023-09-22 12:37:34 -07:00
committed by Joey Yandle
parent 959a6e67f0
commit b848aa5307

View File

@@ -95,7 +95,7 @@ fn spawn_running_signer(path: &PathBuf) -> SpawnedSigner {
RunLoop<FrostCoordinator<v2::Aggregator>>,
StackerDBEventReceiver,
> = Signer::new(runloop, ev, cmd_recv, res_send);
let endpoint = config.node_host;
let endpoint = config.endpoint;
let running_signer = signer.spawn(endpoint).unwrap();
SpawnedSigner {
running_signer,
@@ -228,7 +228,11 @@ fn handle_dkg_sign(args: SignArgs) {
fn handle_run(args: RunDkgArgs) {
debug!("Running signer...");
let _spawned_signer = spawn_running_signer(&args.config);
println!("Signer spawned successfully. Waiting for messages to process.");
println!("Signer spawned successfully. Waiting for messages to process...");
loop {
std::thread::sleep(Duration::from_secs(20));
debug!("Signer still running...");
}
}
fn handle_generate_files(args: GenerateFilesArgs) {