-
Notifications
You must be signed in to change notification settings - Fork 902
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
gossipd: Do not send warning when node_announcement parsing fails #5925
Conversation
Changelog-Fixed: gossip: We removed a warning for old `node_announcement` that was causing LND peers to disconnect
Is there a specific issue with |
Not quite sure myself, there seem to be some really old announcements that are missing something. I'll see which ones result in a warning based on the historian injector and report back what the specific issue is 👍 |
Found at least one:
And decoded:
So we sort of assume that the lease announcements are correct. Rejecting is likely still the correct response, but we should also suppress the warning until LND knows how to handle them (I assume it's mostly a deployment thing rather than the speed for them to implement). |
Thanks for verifying! ACK 4e77168 |
Ok, found a couple more failures where Total population:
Failures:
I can check these again against newer snapshots as the network evolves. And the warning can be re-introduced once lnd doesn't get as upset about it. |
Followup for #5897, since
node_announcement
parsing could result in a warning being sent too.