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
Logs written out of order #1903
Comments
I've tried to reproduce this, could you add a script that verifies it? |
My original post contains literally all of the code to reproduce it. The only thing absent is to I just built a project from the code I posted previously and saw the problem within 4 iterations of |
I've watched it for 20 runs and got nothing. What version of Node.js / Operating System are you using? |
Interesting. |
Video: Edit: Video won't play in my browser, but I can download it and play it in VLC. |
I can't really help. I watched the repro for 1 minute and couldn't see a log out of order. Given the code we have, I couldn't even see how the logs could get out of order. Both the parent and child loggers log to the same sonic boom instance, therefore the log lines are by construction in order. You might want to try reproducing by using https://www.npmjs.com/package/sonic-boom directly. If there is a problem with out-of-order logging, it's there. |
I have a simple test project written to evaluate pino.
Often, the logs are written out of order. Notice the primary
logger.fatal
isn't logged until after the child starts logging in the following output:Edit:
I thought I read that synchronous mode is the default.
The text was updated successfully, but these errors were encountered: