Delgan

Hi. This is likely a problem when `enqueue=True` due to some logged exception not being (un)picklable. This issue has been reported in #342 and will be fixed in the next...

Hi @KoBilla. I think multiple processes should not write to the same file, otherwise you will run into problems even with inode checks. It is not possible to build a...

Coincidentally, the problem with `uwsgi` has been fixed very recently: #325 Using Loguru `v0.5.3`, the child processes should no longer hang at exit. If you are still experiencing problems, surely...

Thanks, that will be of great help if I can reproduce the problem!

Great, I can reproduce the problem, thanks! No kidding, the problem seems to be solved with a single line. ```python import flask ``` However, it must be placed in a...

Hi. Which `loguru` version are you using please? The `Record was: None` error message is tricky. It actually means that `loguru` was unable to retrieve the `record` object at the...

> Could `logger.info(None)` or `logger.exception(None)` also triggere this behaviour. A quick test in REPL did not... No, that's not possible. I am convinced that there is something wrong with deserialization....

> I fixed already 2 cases in my application where the __repr__ called during formatting of better_exceptions caused infinite recursion. Is this something that could be fixed on `loguru` side?...

Yep, the calls made to `repr()` are indeed "protected" by a `try / except` block: https://github.com/Delgan/loguru/blob/f31e97142adc1156693a26ecaf47208d3765a6e3/loguru/_better_exceptions.py#L298-L302 So maybe the endless loop you're seeing does not come from that. :confused: Actually,...

> Thats interesting... After removing the repr --> str call i never experienced this issue again... confused Weird. Maybe the exception raised did not inherited from `Exception` (see [Exception hierarchy](https://docs.python.org/3/library/exceptions.html#exception-hierarchy)),...