Change ChannelManager deserialization to return an optional blockhash#810
Change ChannelManager deserialization to return an optional blockhash#810valentinewallace wants to merge 2 commits intolightningdevkit:mainfrom
Conversation
3f06730 to
43c3b01
Compare
43c3b01 to
35a311c
Compare
Codecov Report
@@ Coverage Diff @@
## main #810 +/- ##
=======================================
Coverage 91.02% 91.02%
=======================================
Files 48 48
Lines 25495 25501 +6
=======================================
+ Hits 23207 23213 +6
Misses 2288 2288
Continue to review full report at Codecov.
|
TheBlueMatt
left a comment
There was a problem hiding this comment.
Should probably be done in ChannelMonitors too, no?
If the ChannelManager never receives any blocks, it'll return a default blockhash on deserialization. It's preferable for this to be an Option instead.
6eb2155 to
684e6f5
Compare
|
Needs rebase and the check_commits CI failed. |
See previous commit msg for details.
684e6f5 to
c21b616
Compare
|
There is no fuzz issue that I can see (are you running I also included a commit which updates the docs there, and I'm ACK on the version available there. |
|
See #819. |
If the ChannelManager never receives any blocks, it'll return a default blockhash
on deserialization. It's preferable for this to be an Option instead.