-
Notifications
You must be signed in to change notification settings - Fork 411
Always return failure in update_monitor after funding spend #1130
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 9 commits into
lightningdevkit:main
from
TheBlueMatt:2021-10-mon-fail-after-conf
Dec 6, 2021
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
63698ec
Allow missing-docs on test-only macros
TheBlueMatt 1ce922c
Prefer fully-specified paths in test macros
TheBlueMatt 37c6c18
Continue after a single failure in `ChannelMonitor::update_monitor`
TheBlueMatt 25542b8
Always return failure in `update_monitor` after funding spend
TheBlueMatt 87b6879
Drop `MonitorUpdateErr` in favor of opaque errors.
TheBlueMatt 6bcb270
Make APIError debug output more clear by including the variant
TheBlueMatt fa62775
Add a simple test for ChainMonitor MonitorUpdate-holding behavior
TheBlueMatt 9fe0cf1
Add a test for MonitorEvent holding when they complete out-of-order
TheBlueMatt 1b88f16
Add trivial test of monitor update failure during block connection
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
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.
IIUC, this test would seem more intuitive to me if we checked that no HTLC update messages were generated before the calls to
channel_monitor_updated
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.
Sure, added the relevant
get_and_clear_pending_msg_events
assertion.