Closed greymistcube closed 1 year ago
If Serilog appends a line break after its logging I'm guessing it could be caused by console.log appending a line break again.
Little search shows console.log()
always adds a new line.
console.log(msg)
is equivalent toprocess.stdout.write(msg + '\n').
I have no knowledge on javascript tho. Would this be hard to fix? 😶
Yeah, but since we depend on electron-log
for logging I think it would be tricky. Could we make the Headless emit its own log in the same folder?
Headless does not know about the log folder, so it should be passed as an argument if we want a separate headless log file in the same folder. If we were to do so, then main.log
, the launcher log, does not encompass internal headless behavior, which may or may not be problematic depending on how we want to troubleshoot things.
Another headless issue, closing.
Example:
For whatever reason, redirected captured console output from headless to
main.log
seems to sporadically add additional empty lines. I suspect this is possibly due toSerilog
batch flushing logs.