mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 01:01:12 -07:00
ScottW514
e3d23b8099
BRINGUP's cloud item said a print is capped by the ring and listed the two gaps that closed when it stopped being. It now says what bounds a print (memory, through pulse_reject_threshold_bytes) and what catches a feed that wedges (progress against room, not ring depth), and it names the two new cases that cannot be induced from the bench: a body past the memory guard, because the service has no such job to send, and a wedged feed, because a healthy machine will not stall on request. forgectrl.settings-bounds gains a probe at the far end of the new byte range, so the validator behind those keys is exercised rather than assumed.