mirror of
https://github.com/ElementsProject/lightning.git
synced 2024-11-20 02:27:51 +01:00
048a650a6b
First, we should have a channel_update so we actually do some compaction! (Reported-by @SimonVrouwe). But we should also handle the cases where: 1. A channel_announcement is *not* directly followed by a channel_update (happens when the channel_update is replaced). 2. A node_announcement predates a channel_update for the peer (again, can happen once a channel_update is replaced). 3. A local/private channel_creation is not directly followed by an update. In addition, we might as well check that we can *load* such a store, before compaction. This checks the corner cases which occur in real gossip stores. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
---|---|---|
.. | ||
data | ||
plugins | ||
benchmark.py | ||
btcproxy.py | ||
conftest.py | ||
fixtures.py | ||
requirements.txt | ||
test_closing.py | ||
test_connection.py | ||
test_db.py | ||
test_gossip.py | ||
test_invoices.py | ||
test_misc.py | ||
test_pay.py | ||
test_plugin.py | ||
utils.py |