Skip to content

Fix a few monitor-update failure bugs found by new fuzzer #286

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

Conversation

TheBlueMatt
Copy link
Collaborator

In writing a new fuzz target I dug up a few existing bugs, this fixes two of them with new tests.

@TheBlueMatt
Copy link
Collaborator Author

Needless rebase to make #288 clearly based on this.

Copy link

@ariard ariard left a comment

Choose a reason for hiding this comment

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

Hmm seems it doesn't break further things, it's all I can say because to be honest it isn't the part I've the well most in head. Maybe I should have start by digging chanmon_fail_consistency in #290 first

@TheBlueMatt
Copy link
Collaborator Author

Now based on #294 and #295.

@TheBlueMatt TheBlueMatt force-pushed the 2019-01-monitor-update-fixes branch 2 times, most recently from 9c7a5b5 to 2aa8fea Compare January 21, 2019 19:25
@TheBlueMatt TheBlueMatt added this to the 0.0.8 milestone Jan 21, 2019
@TheBlueMatt TheBlueMatt force-pushed the 2019-01-monitor-update-fixes branch from 2aa8fea to fafabc7 Compare January 21, 2019 22:10
Primarily this fixes the case where we receive an RAA which does
not require a response, allowing us to call monitor_update_failed
without generating pending messages.
@TheBlueMatt TheBlueMatt force-pushed the 2019-01-monitor-update-fixes branch from fafabc7 to 23abe2b Compare January 22, 2019 19:34
@TheBlueMatt
Copy link
Collaborator Author

Rebased so its now freestanding, gonna go ahead and take this.

@TheBlueMatt TheBlueMatt force-pushed the 2019-01-monitor-update-fixes branch from 23abe2b to be8213b Compare January 22, 2019 19:39
@TheBlueMatt TheBlueMatt merged commit 4a4cdc1 into lightningdevkit:master Jan 22, 2019
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.

2 participants