Delgan

@david-shiko The `onerror` argument exists to help with error handling. If an unexpected error occurs, you may want to call `sys.exit()` with a different code based on error type for...

So your app was still running but logs were not written to the file, right? Is there any chance you can look at the `stderr` at the time of the...

Yes, Loguru tries to capture unexpected exception occurring while logging and display them on `stderr`. You may find it useful if you save it somewhere. Still, Loguru is not supposed...

Hey @domevit. I tries to run the snippets you shared locally but I was not able to reproduce the issue you're facing. :confused: Could that be related to the Flask...

You can do so by implementing a custom exception formatting and/or disabling `diagnose` option: [Customizing the formatting of exceptions](https://loguru.readthedocs.io/en/stable/resources/recipes.html#customizing-the-formatting-of-exceptions).

There is currently no "regex based replacement" available for messages. One has to implement it's own filtering handler as described in the ticket you linked. I'm suggesting to do the...

Hi @KongNan. Is it possible to `configure()` your widget and colorize it? You'll probably need to add a handler in charge of creating and colorizing the text. ```python def add_log_to_gui(self,...

I plan to refactor the `enqueue` argument soon, it should fix your issue I think.

The `"in"` is probably part of your `rank` variable or is somehow added by a custom formatter of your sink. It could also maybe being a third library writing concurrently...

Hello @JulianOrteil. Thanks for the extensive bug report! Basically, when `enqueue=True` the log records need to be serialized using [`pickle.dumps()`](https://docs.python.org/3/library/pickle.html#pickle.dumps). This also applies to the logged exception, if any. The...