From a0c64476114261e7a80f132dc759f3ee06b3fd25 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Thu, 23 Jun 2022 20:53:26 +0930 Subject: [PATCH] lightningd: remove overzealous assertion. This is being hit: it's possible if connectd and lightningd get desynchronized, and we'll handle this later when peer is activated. Signed-off-by: Rusty Russell --- lightningd/peer_control.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/lightningd/peer_control.c b/lightningd/peer_control.c index e3cb6c8d3..47789cdc5 100644 --- a/lightningd/peer_control.c +++ b/lightningd/peer_control.c @@ -1169,9 +1169,6 @@ void peer_connected(struct lightningd *ld, const u8 *msg) if (!peer_subds_pending(peer)) connect_succeeded(ld, peer, hook_payload->incoming, &hook_payload->addr); - /* Can't be opening, since we wouldn't have sent peer_disconnected. */ - assert(!peer->uncommitted_channel); - /* Log and update remote_addr for Nat/IP discovery. */ if (hook_payload->remote_addr) { log_peer_info(ld->log, &id, "Peer says it sees our address as: %s",