Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[DO NOT REVIEW] fundingManager: Set up channel barrier on startup if fundingLocked is not yet received #309

Closed
wants to merge 1 commit into from
Closed

[DO NOT REVIEW] fundingManager: Set up channel barrier on startup if fundingLocked is not yet received #309

wants to merge 1 commit into from

Commits on Sep 6, 2017

  1. fundingManager: channel barrier on startup if fundingLocked not received 

    This commit adds a channel barrier on fundingManager startup for
channels that we still haven't received fundingLocked for. This
fixes a bug where we after restarting the fundingManager would
receive the fundingLocked message, and crash when trying to close
the non-existing barrier.

The fundingmanager tests are also updated to check that the
fundingLocked messages are sent and handled correcly, and also
exercise the scanario described above.
    @halseth
    halseth committed Sep 6, 2017
    Configuration menu
    Copy the full SHA
    2bd7027 View commit details
    Browse the repository at this point in the history