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 <rusty@rustcorp.com.au>
This commit is contained in:
parent
acc78397eb
commit
a0c6447611
|
@ -1169,9 +1169,6 @@ void peer_connected(struct lightningd *ld, const u8 *msg)
|
||||||
if (!peer_subds_pending(peer))
|
if (!peer_subds_pending(peer))
|
||||||
connect_succeeded(ld, peer, hook_payload->incoming, &hook_payload->addr);
|
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. */
|
/* Log and update remote_addr for Nat/IP discovery. */
|
||||||
if (hook_payload->remote_addr) {
|
if (hook_payload->remote_addr) {
|
||||||
log_peer_info(ld->log, &id, "Peer says it sees our address as: %s",
|
log_peer_info(ld->log, &id, "Peer says it sees our address as: %s",
|
||||||
|
|
Loading…
Reference in New Issue