Uh oh!
There was an error while loading. Please reload this page.
Store Payee info with HTLCs - #1138
Conversation
Codecov Report
@@ Coverage Diff @@## main #1138 +/- ##
==========================================
+ Coverage 90.41% 90.47% +0.06%
==========================================
Files 68 68 Lines 35244 35273 +29 ==========================================
+ Hits 31865 31914 +49 + Misses 3379 3359 -20
Continue to review full report at Codecov.
|
6a026ca to
61ed11aCompareTheBlueMatt
commented
Oct 25, 2021
Rebased and fixed fuzz build. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
`Payee` is expected to be used by users to get routes for payment retries, potentially with their own router. Thus, its helpful if it is pub, even if it is redundant with the last hop in the `path` field in `Events::PaymentPathFailed`.
61ed11a to
2a7ed23CompareTheBlueMatt
commented
Oct 25, 2021
Good catch, testing the retry data in the expect macros is super trivial and easy way to get lots of coverage, done. |
This stores and tracks HTLC payee information with HTLCSource info, allowing us to provide it back to the user if the HTLC fails and ensuring persistence by keeping it with the HTLC itself as it passes between Channel and ChannelMonitor.
2a7ed23 to
1b99c93CompareTheBlueMatt
commented
Oct 25, 2021
Squashed without change, will land after CI: |
Based on #1134, this builds on #1104 and ensures users always get payee information back in
PaymentPathFailedevents.