> If the unwrap hadn't caused an exit, the process would've run out of memory It was trying to push an element into a full ArrayVec. The options are: - Blindl

> If the unwrap hadn't caused an exit, the process would've run out of memory It was trying to push an element into a full ArrayVec. The options are: - Blindly write off the end of the array. Obviously no one wants this, despite the decades of tradition... - Panic and unwind, as the program actually did in this case. - Return an error. Some folks assume that returning an error instead of unwinding would've been better. But my assumption is that the outcome would've been the same. I think the issue came up when loading configs, which isn't usually a recoverable situation. If you have an "invalid config error", you're probably just going to return that all the way up, which is effectively the same outcome as unwinding: your process exits with an error code. There are cases where the difference matters a lot, but I don't think this was one of them. The real gap seems to be why it took hours for folks to notice that this service was crash looping. That should normally be really prominent in alerts and dashboards. (Probably part of the story is that alerts were firing all over the place. Tough day at the office.)