bug#77283: Shepherd can't parse logs.

Hi, Ludovic Courtès skribis: > The code that throws that out-of-range exception on ‘substring’ is > (match:substring m 3) in ‘parse-system-log-message’. > > Normally, ‘regexp-exec’ returns match structures with correct > boundaries, but in this case it didn’t. I reported it here: > > https://

bug#77283: Shepherd can't parse logs.

Hi MSavoritias, MSavoritias skribis: > Shepherd has been crashing our system with the message: > > https://upload.magicbroccoli.de/fb6e7843fef693538a5c7c156c0a98fc0aeb6bac/KmA7ovtC2Fcw0Nm0PSCtphwSyDLI1VUF3QrT9PtD/Kuvakaappaus_-_2025-03-26_13-27-11.png > > > This ends up with prosody and openssh

bug#77283: Shepherd can't parse logs.

Shepherd has been crashing our system with the message: https://upload.magicbroccoli.de/fb6e7843fef693538a5c7c156c0a98fc0aeb6bac/KmA7ovtC2Fcw0Nm0PSCtphwSyDLI1VUF3QrT9PtD/Kuvakaappaus_-_2025-03-26_13-27-11.png This ends up with prosody and openssh crashing, nginx still working. the picture show