-
Notifications
You must be signed in to change notification settings - Fork 407
Make errors actionable when failing to deserialize a ChannelManager #976
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
Make errors actionable when failing to deserialize a ChannelManager #976
Conversation
Codecov Report
@@ Coverage Diff @@
## main #976 +/- ##
==========================================
- Coverage 90.63% 90.47% -0.16%
==========================================
Files 60 60
Lines 30538 30607 +69
==========================================
+ Hits 27678 27692 +14
- Misses 2860 2915 +55
Continue to review full report at Codecov.
|
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.
Otherwise SGTM
We changed the sort order of log levels to be more natural, but this comparison wasn't updated accordingly. Likely the reason it was left strange for so long is it also had the comparison argument ordering flipped.
b918220
to
e8110ab
Compare
Squashed without diff:
|
ACK e8110ab For the records about e8110ab, it has been there since #91 : https://github.com/rust-bitcoin/rust-lightning/pull/91/files#diff-8b7223022de62dd3acad8a134eb6fc1cb291b0144df8fb0bb63c454860471a77R167 |
That specific code yes, but I naively swapped the sort order of log levels in #965, which caused the regression. |
See #965 (comment)