rgb-cln/onchaind
Rusty Russell 4eb1233ccb lightningd: don't report spurious temporary_node_failure on local failures.
I noticed the following in logs for tests/test_connection.py::test_feerate_stress:

```
DEBUG 022d223620a359a47ff7f7ac447c85c46c923da53389221a0054c11c1e3ca31d59-chan#1: Failing HTLC 18446744073709551615 due to peer death
DEBUG 022d223620a359a47ff7f7ac447c85c46c923da53389221a0054c11c1e3ca31d59-chan#1: local_routing_failure: 8194 (WIRE_TEMPORARY_NODE_FAILURE)
```

This is because it reports the (transient) node_failure error, because
our channel_failure message is incomplete.  Fix this wart up.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-05-04 18:56:33 +09:30
..
test lightningd: don't report spurious temporary_node_failure on local failures. 2020-05-04 18:56:33 +09:30
Makefile common: use struct onionreply. 2020-01-23 16:17:42 +10:30
onchain_types.h elements: Tell onchaind it may ignore fee outputs 2019-10-03 04:32:57 +00:00
onchain_wire.c onchaind: include htlc id in htlc_stub so we agree on what HTLC we're closing. 2018-10-23 16:55:35 +02:00
onchain_wire.csv df: rename 'funder' to 'opener' 2020-05-04 10:22:26 +09:30
onchain_wire.h onchaind: include htlc id in htlc_stub so we agree on what HTLC we're closing. 2018-10-23 16:55:35 +02:00
onchaind.c df: rename 'funder' to 'opener' 2020-05-04 10:22:26 +09:30