-
Notifications
You must be signed in to change notification settings - Fork 385
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
Correct payment resolution after on chain failure of dust HTLCs #1691
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. |
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.
Looks good, test fails as expected on main
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. 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.
118f418
to
b0a0955
Compare
Oops lol I guess there was a reason the channel was being opened 0conf in the test. |
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. Fixes lightningdevkit#1653.
Squashed without further changes. |
b0a0955
to
a795e45
Compare
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.