lightning

4817 Commits

55 Branches

107 Tags

38 MiB

Tree: bed7986650

Commit Graph

Author	SHA1	Message	Date
Rusty Russell	c8aa50a382	gossipd: fix routing issue. I had a routing problem, and wrote a simple unit test which passed. So I wrote one which copied the failure case (and importantly, had a non-1 fee factor), which triggerd it. In that real example, we underflowed which resulted in us not finding a route. Simply don't consider routes which are infinite. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
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>	8 years ago
Rusty Russell	bbed5e3411	Rename subdaemons, move them into top level. We leave the build results in lightningd/ for ease of in-place testing though. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago

Author

SHA1

Message

Date

Rusty Russell

c8aa50a382

gossipd: fix routing issue.

I had a routing problem, and wrote a simple unit test which passed.  So
I wrote one which copied the failure case (and importantly, had a non-1
fee factor), which triggerd it.

In that real example, we underflowed which resulted in us not finding
a route.  Simply don't consider routes which are infinite.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

8 years ago

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>

8 years ago

Rusty Russell

bbed5e3411

Rename subdaemons, move them into top level.

We leave the *build* results in lightningd/ for ease of in-place testing though.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

8 years ago

503 Commits (bed7986650a8e26935d1f25274a463b94fd5b8a1)