Skip to content

Misc Tweaks #253

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
merged 3 commits into from
Nov 16, 2018
Merged

Conversation

TheBlueMatt
Copy link
Collaborator

Add a bit of test, clarify some internal interfaces somewhat and panic on misuse if the user creates funding transactions which aren't witness-inputs-only as requested by @ariard.

I thought I found a bug in one-side-funded-first reconnect, but
seems I can't reproduce it here. Either way worth improving the
test coverage.
@@ -6636,20 +6636,28 @@ mod tests {
_ => panic!("Unexpected event"),
}

reconnect_nodes(&nodes[0], &nodes[1], (false, true), (0, 0), (0, 0), (0, 0), (0, 0), (false, false));
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What was the kind of bug ? (for the record if one of us beach on it again)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw some issue running rust-lightning-bitcoincorerpc opening an outbound channel then restarting when the remote side had sent its funding_locked but we had not yet sent ours.

@ariard
Copy link

ariard commented Nov 15, 2018

ACK, good to protect user against its own mistakes

@TheBlueMatt TheBlueMatt merged commit b14baa0 into lightningdevkit:master Nov 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants