Skip to content

gossipd: tell lightningd about all our previous channel_updates at startup #6456

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

Merged

Conversation

rustyrussell
Copy link
Contributor

@rustyrussell rustyrussell commented Jul 28, 2023

This will at least help the case where these were not populated, causing us to send errors without channel_updated appended.

It's not perfect: we can still send such errors if the gossip store is corrupted, and we still send them for private channels, but it should help.

(The much better fix is far more invasive, so slips to next release!)
See: #5822

@rustyrussell rustyrussell added this to the v23.08 milestone Jul 28, 2023
…artup.

This will at least *help* the case where these were not populated, causing us
to send errors without channel_updated appended.

It's not perfect: we can still send such errors if the gossip store is
corrupted, and we still send them for private channels, but it should
help.

(The much better fix is far more invasive, so slips to next release!)

Signed-off-by: Rusty Russell <[email protected]>
Copy link
Collaborator

@endothermicdev endothermicdev left a comment

Choose a reason for hiding this comment

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

Pushed a spelling fix in the csv comment.

ACK 0b569e7

@rustyrussell rustyrussell merged commit 4b4937b into ElementsProject:master Jul 29, 2023
@litch
Copy link
Contributor

litch commented Jul 31, 2023

Testing #6253 yesterday I found a number of cases of “this node is surprised at the spend state of its own spliced channel at startup”. I wonder if it’s related to this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants