Merge pull request #6082 from yyforyongyu/6000-peer-conn

peer: fix competing connections to the same peer
This commit is contained in:
Oliver Gugger authored and GitHub committed 2022-01-03 13:28:45 +01:00
commit 9d6701be2b
8 files changed
+100 -39

No files matched your search

+12 -8
View File
@@ -1,13 +1,5 @@
# Release Notes
## Bug Fixes
* [Return the nearest known fee rate when a given conf target cannot be found
from Web API fee estimator.](https://github.com/lightningnetwork/lnd/pull/6062)
* [We now _always_ set a channel type if the other party signals the feature
bit](https://github.com/lightningnetwork/lnd/pull/6075).
## Wallet
* A bug that prevented opening anchor-based channels from external wallets when
@@ -31,6 +23,12 @@
## Bug fixes
* [Return the nearest known fee rate when a given conf target cannot be found
from Web API fee estimator.](https://github.com/lightningnetwork/lnd/pull/6062)
* [We now _always_ set a channel type if the other party signals the feature
bit](https://github.com/lightningnetwork/lnd/pull/6075).
* [Add json flag to
trackpayment](https://github.com/lightningnetwork/lnd/pull/6060)
* [Clarify invalid config timeout
@@ -47,6 +45,12 @@
* [Fix Postgres context cancellation](https://github.com/lightningnetwork/lnd/pull/6108)
* A conflict was found in connecting peers, where the peer bootstrapping
process and persistent connection could compete connection for a peer that
led to an already made connection being lost. [This is now fixed so that
bootstrapping will always ignore the peers chosen by the persistent
connection.](https://github.com/lightningnetwork/lnd/pull/6082)
## RPC Server
* [ChanStatusFlags is now