-
Notifications
You must be signed in to change notification settings - Fork 411
Fix announcements of our own gossip #1169
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
Changes from all commits
74828d2
8f89371
391fbfb
d2ac683
0fe2aef
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -715,6 +715,10 @@ pub enum ErrorAction { | |
/// The peer did something harmless that we weren't able to meaningfully process. | ||
/// If the error is logged, log it at the given level. | ||
IgnoreAndLog(logger::Level), | ||
/// The peer provided us with a gossip message which we'd already seen. In most cases this | ||
/// should be ignored, but it may result in the message being forwarded if it is a duplicate of | ||
/// our own channel announcements. | ||
IgnoreDuplicateGossip, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm I think just There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, its used in a field titled |
||
/// The peer did something incorrect. Tell them. | ||
SendErrorMessage { | ||
/// The message to send. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I was debugging the CI hang, I got as far as figuring out that this is the line that it loops on repeatedly (unless it's repeatedly erroring on
fs::read
). So, I think this patch would fix CI (though IDK what problem that might indicate in theFilesystemPersister
)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least for the purposes of this PR, the issue is that the
ChannelManager
can now change out from under us - theChannelManager
changes by a byte or two after one or two timer ticks, and thus the original version written at the top of the loop isn't necessarily the version that gets written to disk. It's not actually an issue, though.