pub const COUNT_LOG_REFUSED_REASON: &str = "this peer refused a push of the count-cut log, whose pushes carry at \
most `max_batch_events` events of at most three bytes each: its declared \
batch limits are not the limits it imposes, which SY-18's \
`peer_takes_a_batch_at_its_declared_limits` judges, and the log showed no \
page; SY-37 is unverified for this peer";Expand description
The reason SY-37’s rule reports when the peer refused its count-cut log.
That log pushes at most PeerLimits::max_batch_events events of at most
three payload bytes to a push, so a refusal is the peer stating batch
limits it does not impose. SY-18’s batch rule judges that:
peer_takes_a_batch_at_its_declared_limits pushes max_batch_events
events at once, at least as many as any push of this log carries, since
MAX_PROVOKED_BATCH_EVENTS is above the log’s 257, and fails a peer that
refuses them. This skip names the refusal for SY-37’s own sake, and only
when the byte-cut log did not page: a byte-cut log that paged makes the
rule RuleOutcome::Ran. When both logs are refused this is the reason
given, because a refused byte-cut log fails peer_declares_its_own_limits
as well.