Delgan

Hi. Sorry but I'm not familiar with Marimo. Is this issue specific to Loguru or does it happen with any third-party library? Could you maybe please share a minimal reproducible...

Hi @dorschw. Sorry for the late answer. Do you have maybe a minimal reproducible example to share? I don't have any issues with using a custom `compression` function, even when...

Hi @kiml. Thank you for your detailed feedback. I completely agree with you, it is not acceptable that the application could crash because of arbitrary logged message. Using a generic...

> I'm not sure what distinct cases define 'malformed' Basically, I meant something like this should not be swallowed by Loguru: ```python logger.info("Addition: {} + {} = {}", 1, 2)...

@ChuckJonas Formatting of `**kwargs` will be removed altogether, therefore a configuration option shouldn't even be necessary. Are you able to identify the logging messages containing braces through a regex maybe?...

Closing seems I assume you're referring to this library: [`nb_log`](https://github.com/ydf0509/nb_log).

Hey @nathanielobrown. I apologize for the delayed response to such a critical issue that is a possible deadlock. Thanks for your initial analysis. I've been warping my head around the...

Hi. Sorry but I'm not familiar with SeqLog. A minimal but complete example of your code would help me better understand the problem you're facing. In the meantime, here is...

Hi @kivdev, thanks for investigating the issue and proposing a fix. The underlying problem, as you understood, is that each worker runs its own instance of the log file handler....