-
Notifications
You must be signed in to change notification settings - Fork 407
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
Fix a few monitor-update failure bugs found by new fuzzer #286
Conversation
b56f05b
to
afdff76
Compare
Needless rebase to make #288 clearly based on this. |
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.
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
afdff76
to
23eddc8
Compare
9c7a5b5
to
2aa8fea
Compare
2aa8fea
to
fafabc7
Compare
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.
fafabc7
to
23abe2b
Compare
Rebased so its now freestanding, gonna go ahead and take this. |
23abe2b
to
be8213b
Compare
In writing a new fuzz target I dug up a few existing bugs, this fixes two of them with new tests.