rgb-cln/gossipd/test
Rusty Russell ca53c1b699 gossipd: push our own gossip messages harder.
I had a report of a 0.7.2 user whose node hadn't appeared on 1ml.  Their
node_announcement wasn't visible to my node, either.

I suspect this is a consequence of recent version reducing the amount of
gossip they send, as well as large nodes increasingly turning off gossip
altogether from some peers (as we do).  We should ignore timestamp filters
for our own channels: the easiest way to do this is to push them out
directly from gossipd (other messages are sent via the store).

We change channeld to wrap the local channel_announcements: previously
we just handed it to gossipd as for any other gossip message we received
from our peer.  Now gossipd knows to push it out, as it's local.

This interferes with the logic in tests/test_misc.py::test_htlc_send_timeout
which expects the node_announcement message last, so we generalize
that too.

[ Thanks to @trueptolmy for bugfix! ]
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-14 15:00:37 -05:00
..
.gitignore gossipd/test/run-bench-find_route: don't abort if we try to route to ourselves 2017-12-20 13:57:28 +01:00
Makefile gossipd: test vectors for https://github.com/lightningnetwork/lightning-rfc/pull/557 2019-08-10 02:48:34 +00:00
run-bench-find_route.c gossipd: simplify seeker state machine. 2019-10-10 21:48:52 -05:00
run-crc32_of_update.c gossipd: push our own gossip messages harder. 2019-10-14 15:00:37 -05:00
run-extended-info.c gossipd: simplify seeker state machine. 2019-10-10 21:48:52 -05:00
run-find_route-specific.c gossipd: simplify seeker state machine. 2019-10-10 21:48:52 -05:00
run-find_route.c gossipd: simplify seeker state machine. 2019-10-10 21:48:52 -05:00
run-next_block_range.c queries: make sure scids are in order. 2019-10-10 21:48:52 -05:00
run-overlong.c gossipd: simplify seeker state machine. 2019-10-10 21:48:52 -05:00
run-txout_failure.c gossipd: simplify seeker state machine. 2019-10-10 21:48:52 -05:00