Fail to deserialize ChannelManager if it is ahead of any monitor(s)#554
Merged
TheBlueMatt merged 2 commits intolightningdevkit:masterfrom Mar 20, 2020
Merged
Conversation
|
Test don't build but otherwise Concept ACK |
If any monitors are out of sync with the Channel, we previously closed the channel, but we should really only do that if the monitor is ahead of the channel, opting to call the whole thing invalid if the channel is ahead of the monitor.
TheBlueMatt
force-pushed
the
2020-03-stale-mon-fail-man-deser
branch
from
908a759 to
0335d61
Compare
TheBlueMatt
force-pushed
the
2020-03-stale-mon-fail-man-deser
branch
from
0335d61 to
4aa95af
Compare
Collaborator
Author
|
Test should be good now without NLL. Sorry about that. |
|
SGTM 4aa95af |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If any monitors are out of sync with the Channel, we previously
closed the channel, but we should really only do that if the
monitor is ahead of the channel, opting to call the whole thing
invalid if the channel is ahead of the monitor.
As requested by @ariard at #551 (comment)