Skip to content
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

Make pay repeat on routing failure #993

Merged
merged 6 commits into from
Feb 16, 2018
Merged

Conversation

ZmnSCPxj
Copy link
Collaborator

@ZmnSCPxj ZmnSCPxj commented Feb 14, 2018

Fixes: #863

  • Generalize send_payment internal interface.
  • Move pay command handling to a new lightning/payalgo.c system.
  • Make pay repeat.

Intent is to make improvements to pay algorithm in the future to become easier:

@ZmnSCPxj ZmnSCPxj changed the title [WIP] Make pay repeat on routing failure Make pay repeat on routing failure Feb 15, 2018
@Sjors
Copy link
Contributor

Sjors commented Feb 15, 2018

This seems quite useful.

I tried making a payment to mainnet Yalls using this PR and got Could not find a route (on master I get a variety of error messages and long hangs).

Making a donation to Recksplorer did work after 6 (automated) tries (on master it usually fails).

Copy link
Member

@cdecker cdecker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent patchset as always @ZmnSCPxj, I'll let @rustyrussell merge this once he had a chance to review as well.

ACK 02ba654

lightningd/pay.c Outdated
static struct sendpay_command *
new_sendpay_command(struct command *cmd,
new_sendpay_command(const tal_t *cxt,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: cxt -> ctx

@cdecker
Copy link
Member

cdecker commented Feb 16, 2018

ACK 02ba654

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants