core-lightning/gossipd
Rusty Russell 8928f0b5f9 gossipd: remove gossip entirely if we hit a problem on load.
The crashes in #2750 are mostly caused by us trying to partially truncate
the store.  The simplest fix for release is to discard the whole thing if
we detect a problem.

This is a workaround: it'd be far nicer to try to recover.

Fixes: #2750
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-21 22:03:35 +00:00
..
test bitcoin/tx: use fromwire_fail in pull_bitcoin_tx. 2019-06-21 03:56:59 +00:00
broadcast.h gossipd: remove broadcast map altogether. 2019-06-04 01:29:39 +00:00
gossip_constants.h Use node_id everywhere for nodes. 2019-04-09 12:37:16 -07:00
gossip_peerd_wire.csv gossipd: don't send gossip stream, let per-peer daemons read it themselves. 2019-06-04 01:29:39 +00:00
gossip_store.c gossipd: remove gossip entirely if we hit a problem on load. 2019-06-21 22:03:35 +00:00
gossip_store.csv gossipd: erase old entries from the store, don't just append. 2019-06-04 01:29:39 +00:00
gossip_store.h gossipd: note if loaded store seems reasonably up-to-date. 2019-06-12 00:37:46 +00:00
gossip_wire.csv gossipd: don't charge ourselves fees when calculating route. 2019-06-11 23:19:11 +00:00
gossipd.c gossipd: be more verbose and less assert()ive on bad node_announcement. 2019-06-21 22:03:35 +00:00
Makefile gossipd: remove broadcast map altogether. 2019-06-04 01:29:39 +00:00
routing.c gossipd: remove gossip entirely if we hit a problem on load. 2019-06-21 22:03:35 +00:00
routing.h gossipd: remove gossip entirely if we hit a problem on load. 2019-06-21 22:03:35 +00:00