Commit 65808fa
committed
fuzz: handle BroadcastChannelUpdate in chanmon
The regression was introduced in d627ce1. That change
switched fee update opcodes in chanmon_consistency from
maybe_update_chan_fees() to timer_tick_occurred(), which can
enqueue BroadcastChannelUpdate events while peers are
disconnected.
The harness already tolerated those events in one delivery
path, but still treated them as unreachable in
push_excess_b_events and disconnect draining. Accept
BroadcastChannelUpdate in those match arms so the fuzz target
no longer panics on valid timer tick driven message queues.
AI tools were used in preparing this commit.1 parent 7ef91d1 commit 65808fa
1 file changed
Lines changed: 3 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1608 | 1608 | | |
1609 | 1609 | | |
1610 | 1610 | | |
| 1611 | + | |
1611 | 1612 | | |
1612 | 1613 | | |
1613 | 1614 | | |
| |||
1894 | 1895 | | |
1895 | 1896 | | |
1896 | 1897 | | |
| 1898 | + | |
1897 | 1899 | | |
1898 | 1900 | | |
1899 | 1901 | | |
| |||
1916 | 1918 | | |
1917 | 1919 | | |
1918 | 1920 | | |
| 1921 | + | |
1919 | 1922 | | |
1920 | 1923 | | |
1921 | 1924 | | |
| |||
0 commit comments