Uh oh!
There was an error while loading. Please reload this page.
Correct payment resolution after on chain failure of dust HTLCs - #1691
Conversation
Codecov Report
@@ Coverage Diff @@## main #1691 +/- ##
==========================================
- Coverage 90.88% 90.78% -0.11%
==========================================
Files 85 85 Lines 46220 47408 +1188 Branches 46220 47408 +1188 ==========================================
+ Hits 42007 43038 +1031 - Misses 4213 4370 +157
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
valentinewallace
left a comment
There was a problem hiding this comment.
Looks good, test fails as expected on main
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.
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.
wpaulino
left a comment
There was a problem hiding this comment.
LGTM. There are a few warnings/failures to fix after the latest push.
Also wrote a commit to create a type alias for the test ChannelManager if you want to include it here, see https://gist.github.com/wpaulino/edc59a12b749452d8bcce2bb0816cee2.
Uh oh!
There was an error while loading. Please reload this page.
118f418 to
b0a0955CompareTheBlueMatt
commented
Sep 6, 2022
Oops lol I guess there was a reason the channel was being opened 0conf in the test. |
wpaulino
commented
Sep 6, 2022
Feel free to squash. |
Previously, we wouldn't mark a dust HTLC as permanently resolved if the commitment transaction went on chain. This resulted in us always considering the HTLC as pending on restart, when we load the pending payments set from the monitors. Fixeslightningdevkit#1653.
TheBlueMatt
commented
Sep 6, 2022
Squashed without further changes. |
b0a0955 to
a795e45Compare
Previously, we wouldn't mark a dust HTLC as permanently resolved if
the commitment transaction went on chain. This resulted in us
always considering the HTLC as pending on restart, when we load the
pending payments set from the monitors.
Fixes#1653.