This expands on #18672 in two ways:
- Check positive cases (
filterloadaccepted,filteraddaccepted) in addition to the negative cases added in #18672 - Address MarcoFalke 's suggestion to successfully load a filter before testing
filteradd
This expands on #18672 in two ways:
filterload accepted, filteradd accepted) in addition to the negative cases added in #18672filteradd<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
No conflicts as of last run.
Concept ACK -- nit: now with so many small tests for checking the size limits, you could put them all in a new method of the test?
Good idea, updated! And thanks for the review.
83 | + with self.nodes[0].assert_debug_log(['Misbehaving']): 84 | + filter_node.send_and_ping(msg_filterload(data=b'\xaa', nHashFuncs=MAX_BLOOM_HASH_FUNCS+1)) 85 | + 86 | + self.log.info('Check that filter with max hash functions is accepted') 87 | + with self.nodes[0].assert_debug_log([], unexpected_msgs=['Misbehaving']): 88 | + filter_node.send_and_ping(msg_filterload(data=b'\xaa', nHashFuncs=MAX_BLOOM_HASH_FUNCS, nTweak=0, nFlags=1))
nit: explicitely setting nTweak and nFlags is not needed here
Fixed, thanks!