Matt Corallo be6f263825 Remove the peer_disconnected no_connection_possible flag ... Long ago, we used the `no_connection_possible` to signal that a peer has some unknown feature set or some other condition prevents us from ever connecting to the given peer. In that case we'd automatically force-close all channels with the given peer. This was somewhat surprising to users so we removed the automatic force-close, leaving the flag serving no LDK-internal purpose. Distilling the concept of "can we connect to this peer again in the future" to a simple flag turns out to be ripe with edge cases, so users actually using the flag to force-close channels would likely cause surprising behavior. Thus, there's really not a lot of reason to keep the flag, especially given its untested and likely to be broken in subtle ways anyway.		2023-02-21 19:17:06 +00:00
..
src	Remove the peer_disconnected no_connection_possible flag	2023-02-21 19:17:06 +00:00
Cargo.toml	Always set _test_utils when building lightning for some tests	2023-01-18 16:57:50 -08:00