You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sink produces missing or partial console output when the current size of the log is less than the size of the buffer of the StreamWriter used to write to the console's stdout stream.
Expected behavior
Each log message should appear in the console in its entirety shortly after it has been generated by the application.
Actual behavior
The last line in the console output contains a partial log message. Generating more log messages completes the line.
Steps to reproduce
Start the DemoApp
Notice that no output appears in the console
Send an HTTP GET request to http://localhost:5000
Notice that the last line in the console output shows an incomplete log message
Send another GET request to http://localhost:5000
The incomplete log message now appears in its entirety
The screenshot below shows an example of how it might look like in step 4:
Known workarounds
Generating a constant stream of log messages does not expose this bug.
The text was updated successfully, but these errors were encountered:
ecampidoglio
added a commit
to ecampidoglio/serilog-sinks-fastconsole
that referenced
this issue
Oct 19, 2023
This commit ensures that log messages are printed to the console's
stdout in their entirety by flushing the internal buffer of the
`StreamWriter` after every write operation.
Description
The sink produces missing or partial console output when the current size of the log is less than the size of the buffer of the
StreamWriter
used to write to the console's stdout stream.Expected behavior
Each log message should appear in the console in its entirety shortly after it has been generated by the application.
Actual behavior
The last line in the console output contains a partial log message. Generating more log messages completes the line.
Steps to reproduce
DemoApp
http://localhost:5000
http://localhost:5000
The screenshot below shows an example of how it might look like in step 4:
Known workarounds
Generating a constant stream of log messages does not expose this bug.
The text was updated successfully, but these errors were encountered: