-
Notifications
You must be signed in to change notification settings - Fork 268
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
Do not include optional timestamp/checksum TLV if they are empty #1280
Conversation
I'll make it ready for review as soon as I've added proper tests |
Codecov Report
@@ Coverage Diff @@
## master #1280 +/- ##
==========================================
+ Coverage 77.11% 77.17% +0.06%
==========================================
Files 142 142
Lines 9934 9934
Branches 417 417
==========================================
+ Hits 7661 7667 +6
+ Misses 2273 2267 -6
|
eclair-core/src/test/scala/fr/acinq/eclair/router/ChannelRangeQueriesSpec.scala
Outdated
Show resolved
Hide resolved
Test against c-lighting (at ElementsProject/lightning@4be1868) and lnd (https://github.com/lightningnetwork/lnd/releases/tag/v0.9.0-beta-rc2) |
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.
LGTM
Don't include optional timestmap or checksum TLVs if they are empty (i.e. there are no scids in the current block range)
I think previous implementation made more sense. How can I tell now that my peer understood that I requested additional data, but just doesn't have any? |
This change fixes an interop issue with c-lighting, which does not handle
reply_channel_range
messages that include an optiontimestamps
TLV that contains an empty array of timestamps with aZLIB
encodingand fails with a
connection-level error, failing all channels! reason=reply_channel_range 0 timestamps when 0 scids?` errorIt is related to lightning/bolts#729