I just noticed because this is causing Picard PR tests to fail.
2025-11-09 31311, 2025
rdswift[m]
Looks like it's back now.
2025-11-09 31323, 2025
relaxo[m] joined the channel
2025-11-09 31323, 2025
relaxo[m]
So i just noticed, that I need to migrate from Hilt to Koin for Muliplatform.
2025-11-09 31323, 2025
relaxo[m]
I think that will be my first step towards that direction.
2025-11-09 31313, 2025
julian45[m] joined the channel
2025-11-09 31314, 2025
julian45[m]
<Jade[m]> "It had literally just never hand..." <- yeah!! plus, i'm not sure whether the recent delivery failure is even actionable on our end, as lettre's address validator seemed to think the target address was fine (or else we should have gotten a `lettre::address::AddressError`, right?), and smtp 550 is a result of the *recipient's* mail server denying the message
2025-11-09 31339, 2025
Jade[m]
julian45[m]: Yep, exactly
2025-11-09 31347, 2025
julian45[m]
though it would be nice to get the "offending" email address as part of logs
2025-11-09 31307, 2025
Jade[m]
The way to 'fix' taht would be to more strictly validate the emails in mbs / the UI lol
2025-11-09 31318, 2025
Jade[m]
julian45[m]: PII, so probably a bad idea
2025-11-09 31318, 2025
julian45[m]
in general, perhaps, but anyone who would even have a chance of getting at that data would have signed a contract with MB that permits them to view such pii under strict secrecy terms, and this is the sort of thing that would be useful in attempting to "debug" what we can from our end
2025-11-09 31340, 2025
julian45[m]
plus we wouldn't even retain such logs for long anyway
2025-11-09 31313, 2025
julian45[m]
* in general, perhaps, but anyone who would even have a chance of getting at that data through, say, a log search server or by poring through docker logs would have signed a contract with MeB that permits them to view such pii under strict secrecy terms, and this is the sort of thing that would be useful in attempting to "debug" what we can from our end
