mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-02-27 08:28:49 +01:00
6e7000c5e7
When generating a `channel_update` either in response to a fee configuration change or an HTLC failure, we currently poll the channel to check if the peer's connected when setting the disabled bit in the `channel_update`. This could cause cases where we set the disable bit even though the peer *just* disconnected, and don't generate a followup broadcast `channel_update` with the disabled bit unset. While a node generally shouldn't rebroadcast a `channel_update` it received in an onion, there's nothing inherently stopping them from doing so. Obviously in the fee-update case we expect the message to propagate. Luckily, since we already "stage" disable-changed updates, we can check the staged state and use that to set the disabled bit in all `channel_update` cases. |
||
|---|---|---|
| .. | ||
| chan_utils.rs | ||
| chanmon_update_fail_tests.rs | ||
| channel.rs | ||
| channelmanager.rs | ||
| features.rs | ||
| functional_test_utils.rs | ||
| functional_tests.rs | ||
| inbound_payment.rs | ||
| mod.rs | ||
| monitor_tests.rs | ||
| msgs.rs | ||
| onion_route_tests.rs | ||
| onion_utils.rs | ||
| outbound_payment.rs | ||
| payment_tests.rs | ||
| peer_channel_encryptor.rs | ||
| peer_handler.rs | ||
| priv_short_conf_tests.rs | ||
| reload_tests.rs | ||
| reorg_tests.rs | ||
| script.rs | ||
| shutdown_tests.rs | ||
| wire.rs | ||