Closed pellaea closed 2 months ago
Thanks for fixing this. Given all the monkeys banging on all the keyboards, I can see non-utf8 sequences ending up in the log. I can specifically imagine monkeys with bad intent throwing binary data where it shouldn't go.
:) Yep, I'm not overly concerned.
On Wed, May 1, 2024 at 8:35 AM Nathan Wilson @.***> wrote:
Thanks for fixing this. Given all the monkeys banging on all the keyboards, I can see non-utf8 sequences ending up in the log. I can specifically imagine monkeys with bad intent throwing binary data where it shouldn't go.
— Reply to this email directly, view it on GitHub https://github.com/MushroomObserver/mushroom-observer/pull/2124#issuecomment-2088404123, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYTNNLUS4BIX3WGBBLFJDTZADORPAVCNFSM6AAAAABHBGIGX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYGQYDIMJSGM . You are receiving this because you modified the open/close state.Message ID: @.***>
The "real" problem is why are there non-utf8 sequences in the log??? But be that as it may, code should never crash, as a general rule, and I can at least fix that...