-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated send_payment_with_route
API and friends
#3430
Remove deprecated send_payment_with_route
API and friends
#3430
Conversation
151ec49
to
3956661
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3430 +/- ##
==========================================
+ Coverage 89.65% 89.69% +0.04%
==========================================
Files 130 130
Lines 107422 107401 -21
Branches 107422 107401 -21
==========================================
+ Hits 96306 96336 +30
+ Misses 8718 8664 -54
- Partials 2398 2401 +3 ☔ View full report in Codecov by Sentry. |
Nice, basically LGTM, why is this draft? |
Ah, I wanted to make sure the fuzz changes passed CI. Undrafting |
I can also rename |
I like the clear implication in the name - " if you see one of these you can retry" vs just "this failed", I think. |
Looks good to me, too, but there is some weirdness in beta Rust versions in CI. I think it's unrelated though. |
Would you mind rebasing this? I think that should fix all CI issues. |
This method has been deprecated for several versions in favor of ChannelManager::send_payment, and we want to remove it from the public API entirely prior to the 0.1 release. However, >150 tests use it so put off removing the method entirely.
The old API is confusing and we want to remove it for 0.1.
Removes the final usage of PaymentSendFailure from public API. This (confusing) error matched with prior versions of LDK where users had to handle payment retries themselves. Since auto-retry was introduced, the only non-deprecated use remaining was for probe send errors. Probes only have one path, though, so refactor ProbeSendFailure to omit usage of PaymentSendFailure. We don't make this error private yet because it's still used by some fuzzing code as well as internally to outbound_payments, but it isn't returned by any public functions anymore.
This allows us to make the PaymentSendFailure error type private, as well as reduce the visibility of the vestigial send_payment_with_route method that was already made test and fuzz-only in a previous commit.
3956661
to
bcaba29
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Mark the deprecated
ChannelManager::send_payment_with_route
API as test-only, partially addressing #2390.This method has been deprecated for several versions in favor of
ChannelManager::send_payment
, and we want to remove it from the public APIentirely for the 0.1 release.
Also went ahead and removed the old API for
send_spontaneous_payment
that allowed specifying a route, though it wasn't officially deprecated.