-
Notifications
You must be signed in to change notification settings - Fork 402
Block the mon update removing a preimage until upstream mon writes #2169
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 7 commits into
lightningdevkit:main
from
TheBlueMatt:2023-03-monitor-e-monitor
Sep 12, 2023
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4835b16
Fix various unused warnings in test and regular builds
TheBlueMatt e37a400
Clean up test handling of resending responding commitment_signed
TheBlueMatt 5ff51b7
Block the mon update removing a preimage until upstream mon writes
TheBlueMatt 46453bf
Correct `expect_payment_forwarded` upstream channel checking
TheBlueMatt 0d8b096
Update tests to test re-claiming of forwarded HTLCs on startup
TheBlueMatt 6c3029d
Split `expect_payment_forwarded` into a function called by macro
TheBlueMatt 9f3e127
Test monitor update completion actions on pre-startup completion
TheBlueMatt 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
Oops, something went wrong.
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.
Would it be effectively the same to just pass in
counterparty_opt
? It seems like we won't do anything unless the channel is aroundThere 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.
Mmmm, yea, we definitely could, might even be better cause we'd never bother trying to wake a channel that's already been closed. That said, it does feel like the kinda thing we'll screw up in the future trying to use that arg and then end up not calling some important code. At least with the fallback all remotely-recently-deployed nodes will still work? I dunno.