-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Several issues with truncatingFileWriter make it problematic in production environments:
- does not support size based truncation
- time from last truncation is initialized to the system clock on startup - so we never truncate if all runs are short
- loosing recent log data at the time of truncation - no file rolling
- Recovery from
erronTruncateis wrong. in this case the object should probably return an error and just ignore the new "write".
Instead,seek(0,0)only creates corrupt data, and is not checked for error in itself.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels