-
Notifications
You must be signed in to change notification settings - Fork 407
PaymentPathFailed
: add initial send error details
#2043
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
Merged
TheBlueMatt
merged 10 commits into
lightningdevkit:main
from
valentinewallace:2023-02-initial-send-path-fails
Feb 27, 2023
Merged
Changes from 2 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f361aa6
Add missing import path in ser macro
valentinewallace 2037a24
Remove all_paths_failed from PaymentPathFailed
valentinewallace 52551a9
Support deserializing an Option-al MaybeReadable
valentinewallace 0e88538
Disambiguate ignorable and ignorable_option
valentinewallace 70c7161
Rename OptionDeserWrapper->RequiredWrapper
valentinewallace 5d0ee86
Fix upgradable_required fields to actually be required in lower level…
valentinewallace 34f8c39
ser_macros: Document behavior of upgradable_* variants
valentinewallace 8d686d8
Implement writeable for APIError
valentinewallace 1dcb3ec
Change PaymentPathFailed's optional network update to a Failure enum
valentinewallace f2f90d5
Fix PaymentPathFailed generation and scid on initial send
valentinewallace File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
## API Updates | ||
- `Event::PaymentPathFailed::all_paths_failed` has been removed, as we've dropped support for manual | ||
payment retries. | ||
|
||
## Backwards Compatibility | ||
- If downgrading from 0.0.114 to a previous version, `Event::PaymentPathFailed::all_paths_failed` | ||
will always be set to `false`. Users who wish to support downgrading and currently rely on the | ||
field should should first migrate to always calling `ChannelManager::abandon_payment` and awaiting | ||
`PaymentFailed` events before retrying (see the field docs for more info on this approach: | ||
<https://docs.rs/lightning/0.0.113/lightning/util/events/enum.Event.html#variant.PaymentPathFailed.field.all_paths_failed>), | ||
and then migrate to 0.0.114. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
nit:
should should
:)