mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-02-24 23:08:36 +01:00
Allow routefinding again due to HTLC limit based on >= not >
While this doesn't matter much in practice, if we go around again when route-finding to try to meet an htlc_minimum_msat, we use the `recommended_value_msat` which can work if we meet the `htlc_minimum_msat` on a channel exactly, so using >= rather than > can capture cases with 1msat more.
This commit is contained in:
parent
082a19b2d4
commit
5861dde692
1 changed files with 2 additions and 2 deletions
|
@ -1788,9 +1788,9 @@ where L::Target: Logger {
|
||||||
#[allow(unused_comparisons)] // $next_hops_path_htlc_minimum_msat is 0 in some calls so rustc complains
|
#[allow(unused_comparisons)] // $next_hops_path_htlc_minimum_msat is 0 in some calls so rustc complains
|
||||||
let may_overpay_to_meet_path_minimum_msat =
|
let may_overpay_to_meet_path_minimum_msat =
|
||||||
((amount_to_transfer_over_msat < $candidate.htlc_minimum_msat() &&
|
((amount_to_transfer_over_msat < $candidate.htlc_minimum_msat() &&
|
||||||
recommended_value_msat > $candidate.htlc_minimum_msat()) ||
|
recommended_value_msat >= $candidate.htlc_minimum_msat()) ||
|
||||||
(amount_to_transfer_over_msat < $next_hops_path_htlc_minimum_msat &&
|
(amount_to_transfer_over_msat < $next_hops_path_htlc_minimum_msat &&
|
||||||
recommended_value_msat > $next_hops_path_htlc_minimum_msat));
|
recommended_value_msat >= $next_hops_path_htlc_minimum_msat));
|
||||||
|
|
||||||
let payment_failed_on_this_channel = scid_opt.map_or(false,
|
let payment_failed_on_this_channel = scid_opt.map_or(false,
|
||||||
|scid| payment_params.previously_failed_channels.contains(&scid));
|
|scid| payment_params.previously_failed_channels.contains(&scid));
|
||||||
|
|
Loading…
Add table
Reference in a new issue