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
..
Makefile	makefiles: move all unit tests under make check-units	2019-06-30 16:41:30 +09:30
run-find_my_abspath.c	queries: make sure scids are in order.	2019-10-10 21:48:52 -05:00
run-invoice-select-inchan.c	gossipd: push our own gossip messages harder.	2019-10-14 15:00:37 -05:00
run-jsonrpc.c	gossipd: push our own gossip messages harder.	2019-10-14 15:00:37 -05:00