mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-01-18 13:25:43 +01:00
Code Issues Projects Releases Wiki Activity

lightningd: don't log BROKEN when we don't have a channel update.

Browse Source 
This happened on my testnet node because I've been failing to reconnect to
a node which created a channel and never exchanged announcement sigs.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2020-04-05 10:59:21 +09:30 committed by Christian Decker
parent b8262c3de2
commit 117a8391f9
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
lightningd/peer_htlcs.c
View File

@ -157,14 +157,10 @@ static void failmsg_update_reply(struct subd *gossipd,
u8 *stripped_update;
struct failed_htlc *failed_htlc;
/* In theory, we could have no update because channel suddenly closed,
* but it's v. unlikely */
/* This can happen because channel never got properly announced.*/
if (!fromwire_gossip_get_stripped_cupdate_reply(msg, msg,
&stripped_update)
|| !tal_count(stripped_update)) {
log_broken(gossipd->log,
"bad fromwire_gossip_get_stripped_cupdate %s",
tal_hex(msg, msg));
failmsg = towire_temporary_node_failure(NULL);
} else {
/* End of failmsg is two zero bytes (empty update). */