mirror of
https://github.com/mailscope/kumomta.git
synced 2026-09-09 03:52:13 +00:00
Prior to exposing max_burst in the throttle string parser, we couldn't guarantee to represent any arbitrary throttle as a string, so we serialized as the underlying struct fields. That's a bit unwieldy to read, so let's switch to the string representation. This commit makes the string repr infallible (previously it could fail if you had specified max_burst), then tackles the fanout from that. Apparently none of our snapshot tests include any of these throttles, so I manually spot checked it with `kcli inspect-sched-q` to observe the `max_message_rate`.