Include NegotiationFailureReason in InteractiveTxMsgError#4609
Include NegotiationFailureReason in InteractiveTxMsgError#4609wpaulino wants to merge 1 commit intolightningdevkit:mainfrom
Conversation
Each `SpliceNegotiationFailed` event originating from an `InteractiveTxMsgError` needs a `NegotiationFailureReason`, so it makes sense to track it in the same place. In most cases, the `NegotiationFailureReason` included uses the `NegotiationError` variant, but other cases may require their own specific variant, such as `LocallyCanceled` after calling `ChannelManager::cancel_funding_contributed`.
|
👋 Thanks for assigning @TheBlueMatt as a reviewer! |
|
I've thoroughly reviewed the entire PR diff and explored the relevant codebase context. This is a clean refactoring that moves Key verification points:
No issues found. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4609 +/- ##
==========================================
- Coverage 86.12% 86.11% -0.01%
==========================================
Files 157 157
Lines 108824 108841 +17
Branches 108824 108841 +17
==========================================
+ Hits 93721 93725 +4
- Misses 12487 12497 +10
- Partials 2616 2619 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Each
SpliceNegotiationFailedevent originating from anInteractiveTxMsgErrorneeds aNegotiationFailureReason, so it makes sense to track it in the same place. In most cases, theNegotiationFailureReasonincluded uses theNegotiationErrorvariant, but other cases may require their own specific variant, such asLocallyCanceledafter callingChannelManager::cancel_funding_contributed.Fixes #4490 (comment)