-
Notifications
You must be signed in to change notification settings - Fork 1k
Disable channel when losing the underlying connection #756
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
Merged
rustyrussell
merged 9 commits into
ElementsProject:master
from
cdecker:disable-on-shutdown
Jan 26, 2018
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
e6d56ff
channeld: Send disabling channel_update on shutdown
cdecker 84cfb51
channeld: Tell gossipd when we get a shutdown message from a peer
cdecker 238e4c2
masterd: Peer has to know which direction an eventual channel is
cdecker cb7bf5e
gossip: Add message to enable and disable a channel
cdecker 9608240
gossip: Implement handler for enabling and disabling channels
cdecker 5b86ddb
masterd: Disable a channel when channeld fails
cdecker 7813e1f
pytest: Check that we disable on closing and permfail.
cdecker 25bcaeb
pytest: Fix test_pay_disconnect
cdecker f4b14ba
fixup! masterd: Disable a channel when channeld fails
cdecker File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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.
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.
In this case, what if active was true? Did we just enable a channel w/o a channel update?
I think this test should be moved up above the assignment?
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.
Can't do that, otherwise we can only ever deactivate a channel that has reached
announce_depth, i.e., 6 blocks. The channel is activated locally afterfunding_depth, i.e., 2 confirmations. So if we happen to lose the connection or similar, which the channel has 2-5 confirmations we cannot deactivate and we're stuck with a non-functioning channel being returned as part of the routes.If the channel is public, we also have a
channel_updatewhich we can update with the disable flag, if the channel is not public, then others don't care anyway.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.
Good point.
OK, my q still stands. We're asserting that active == false in this branch (based on the msg), we should actually assert that?
I'll apply this now, but please consider...