-
Notifications
You must be signed in to change notification settings - Fork 913
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
channeld: send warning, not error if peer has old commitment number. #5152
channeld: send warning, not error if peer has old commitment number. #5152
Conversation
This title of the PR is misleading, shouldn't it be exactly the opposite (ie |
# l1 should NOT drop to chain, since it didn't receive an error. | ||
time.sleep(5) | ||
assert bitcoind.rpc.getrawmempool(False) == [] | ||
|
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.
l1.daemon.wait_for_logs(["channeld WARNING: bad reestablish revocation_number: 0 vs 3"]) | |
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.
ACK 3532d3d
3532d3d
to
9841485
Compare
Rebased on top of |
9841485
to
0697009
Compare
This is the minimal change to meet the desired outcome of lightning/bolts#934 which wants to give obsolete-db nodes a chance to fix things up, before we close the channel. We need to dance around a bit here, since we *will* close the channel if we receive an ERROR, so we suppress that. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
0697009
to
a551f70
Compare
This is the minimal change to meet the desired outcome of lightning/bolts#934
which wants to give obsolete-db nodes a chance to fix things up, before we
close the channel.
We need to dance around a bit here, since we will close the channel if
we receive an ERROR, so we suppress that.