Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No bad gossip after close #3245

Conversation

rustyrussell
Copy link
Contributor

@rustyrussell rustyrussell commented Nov 6, 2019

Test fixes and an actual gossipd improvement which also fixes tests.

Changelog-none: no user-visible changes

…ossip!

It currently works because we inject it so fast that it's still doing the
txout lookup, but that's about to change.

Signed-off-by: Rusty Russell <[email protected]>
…re options.

And drive-by fix: document that you can now (since
e40f078) use --max-messages=0.

Signed-off-by: Rusty Russell <[email protected]>
This correctly refreshes the txout entry against aging.

Signed-off-by: Rusty Russell <[email protected]>
This prevents a gratuitous lookup of we get a late channel_announce,
but even better, it suppresses the "bad gossip" messages in case of
a late channel_update, which have plagued Travis (especially since we
got aggressive in pushing our own updates).

Signed-off-by: Rusty Russell <[email protected]>
Reduce test_feerate_stress iterations, and simply don't run
test_pay_retry under VALGRIND with SLOW_MACHINE at all.

Signed-off-by: Rusty Russell <[email protected]>
@rustyrussell rustyrussell force-pushed the guilt/no-bad-gossip-after-close branch from c7cd381 to 1e244d5 Compare November 6, 2019 04:15
Copy link
Contributor

@niftynei niftynei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack 1e244d5

@rustyrussell rustyrussell merged commit a70f2dc into ElementsProject:master Nov 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants