brontide: fix peer disconnection issue#9872
brontide: fix peer disconnection issue#9872Roasbeef merged 3 commits intolightningnetwork:masterfrom
Conversation
|
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
yyforyongyu
left a comment
There was a problem hiding this comment.
Thanks for the fix! It looks like it's a cure for #9622.
Pending linter fixes otherwise good to go!
cbf70f2 to
1b7b4aa
Compare
|
Added a simple itest as well which would fail without this new change. |
1b7b4aa to
c308a73
Compare
|
|
||
| // testRBFCoopCloseDisconnect tests that when a node disconnects that the node | ||
| // is properly disconnected. | ||
| func testRBFCoopCloseDisconnect(ht *lntest.HarnessTest) { |
There was a problem hiding this comment.
could you add this test in a separate commit so we could run this test to see it fail?
c308a73 to
b51a790
Compare
Add a connect/disconnect test when the peers both started up with the rbf coop close feature.
In case when the rbf coop close feature was active we would not properly disconnect the peer.
b51a790 to
329c571
Compare
In case when the rbf coop close feature was active we would not
properly disconnect the peer.