core-lightning/gossipd
Rusty Russell 66a07461d3 gossipd: don't ignore first update if timestamp == 0
Since we initialize last_timestamp to 0, we ignore any initial update
with this timestamp.  Don't compare it if we don't already have an
update, and don't initialize it, so valgrind can tell us if we use
it accidentally.

	b'lightning_gossipd(3368): TRACE: Received channel_update for channel 6892:2:1(0)'
	b'lightning_gossipd(3368): TRACE: Ignoring outdated update.'
	b'lightning_gossipd(3368): TRACE: Received channel_update for channel 6893:2:1(1)'
	b'lightning_gossipd(3368): TRACE: Channel 6893:2:1(1) was updated.'

The same logic applies to node_updates, so we do the same there.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-09-03 02:01:54 +02:00
..
broadcast.c Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
broadcast.h Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
gossip.c Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
gossip_wire.csv Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
Makefile Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
routing.c gossipd: don't ignore first update if timestamp == 0 2017-09-03 02:01:54 +02:00
routing.h Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00