Repository navigation
Prevent ChannelForceClosed monitor update error after detecting spend - #2265
Conversation
If we detected a spend for a channel onchain prior to handling its `ChannelForceClosed` monitor update, we'd log a concerning error message and return an error unnecessarily. The channel has already been closed, so handling the `ChannelForceClosed` monitor update at this point should be a no-op.
|
Let's also log in |
a33a1bc to
1aeb821
Compare
Codecov ReportPatch coverage:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #2265 +/- ##
==========================================
- Coverage 91.50% 91.49% -0.01%
==========================================
Files 104 104
Lines 52087 52096 +9
Branches 52087 52096 +9
==========================================
+ Hits 47660 47666 +6
- Misses 4427 4430 +3
☔ View full report in Codecov by Sentry. |
If we detected a spend for a channel onchain prior to handling its
ChannelForceClosedmonitor update, we'd log a concerning error message and return an error unnecessarily. The channel has already been closed, so handling theChannelForceClosedmonitor update at this point should be a no-op.Fixes #2263.