Matteo Collina

Try if this helps at all in your current setup: https://github.com/pinojs/pino/pull/1499. (I don't have a throwaway machine at my disposal, I'd need to set it up for this case)

No, I recommended you to test a patch in pino to verify a theory as I won't have time soon to set up a custom linux system for this test.

Good thing: #1499 will provide a quick-and-dirty solution for you. I wonder a bit why this works at all. https://fhackts.wordpress.com/2014/11/27/systemd-journal-not-showing-python-3-print/ shows a similar problem. In `pino.destination()`, we are not calling...

The idea behaind https://github.com/pinojs/sonic-boom/pull/153 is that somebody that is interested in avoiding any delay they can force an `fsync()` after every write.

The following should now work and fix this problem: ```js const logger = pino({ name: 'bot-sales', timestamp: pino.stdTimeFunctions.isoTime, }, pino.destination({ dest: process.stddout, sync: true, fsync: true })) ```

I'm reopening and tagging as "help wanted". Unfortunately, I've exhausted my time in chasing systemd quirks. A PR that solved this would be awesome. The fix would be: 1. identify...

In a 30 minutes test I just did I experienced the behavior on both. I think it's just how OS works.

Then it's a duplicate of: https://github.com/pinojs/sonic-boom/issues/139. Very likely due to the emoji.

Here is a PR with a partial fix: https://github.com/pinojs/sonic-boom/pull/154

I don't think it's possible at the moment. I would recommend to not read them manually but use pretty-print.