New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error log is slower than others #344
Comments
What is your tinylog configuration? |
Here is my configuration. I tried with enabled and disabled writingthread |
Okay, I just got to the point where I tested my project outside of IntelliJ. Seems like the "bug" only occurs in IntelliJ's console. |
Yes, the console of IntelliJ (and also some other consoles) have this behavior. The standard output stream and the error stream are two independent asynchronous streams. Therefore, it is possible that the output to one of these both streams can overtake the other. tinylog nor any other Java library can change this behavior. However, you reconfigure the console writer to use only the standard output stream or the error stream for all severity levels: writer = console
writer.stream = out # or err Please be aware that this has the disadvantage that all severity levels will have the same color in the console of IntelliJ. By the way, the writing thread can only be enabled globally for all writers. It is not possible to enable it only for a certain writer. writingthread = true |
Describe the bug
When logging an error at the end of a while loop and logging info at the beginning the info message get's displayed first if the loop continues
To Reproduce
Steps to reproduce the behavior:
Environment
tinylog version: 2.5.0
Kotlin version: 1.7.21
The text was updated successfully, but these errors were encountered: