-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
sweep: remove possible RBF when sweeping new inputs #8091
Merged
Roasbeef
merged 11 commits into
lightningnetwork:master
from
yyforyongyu:remove-rbf-sweeper
Oct 25, 2023
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
3997368
sweep: add new method `handleNewInput`
yyforyongyu 39a7cc6
sweep: rename `waitForSpend` to `monitorSpend` to avoid confusion
yyforyongyu f1d0f9f
sweep: add new method `handleInputSpent`
yyforyongyu 62b5869
sweep: add new method `handleSweep`
yyforyongyu 4ba0909
sweep+lnd: move ticker creation into sweeper
yyforyongyu 7de4186
sweep: simplify polling logic in sweeper
yyforyongyu acc15d8
sweep: add new method `rescheduleInputs` and refactor `sweep`
yyforyongyu 9283762
sweep: remove possible RBF when creating sweeping tx for new inputs
yyforyongyu 0816f91
itest: update itest to reflect new sweeper behavior
yyforyongyu 05fbe8b
docs: update release note re RBF fix
yyforyongyu dba4c8e
trivial: fix typo and nits
yyforyongyu 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 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
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.
Why doesn't this try to explicitly catch the double spend error any longer?
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.
Is the rationale that since we reschedule everything above, we don't need to specially handle this control flow?
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.
Exactly we want to make sure, that even
unexpected errors
increase theirattempt counter
allowing them to be removed after the default of 10 attempts (default value). Moreover we use the error to signal, that we try to publish all the new inputs in a separate transaction when the combined one (combination of retried and new inputs) failed.