Skip to content

truncatingFileWriter issues #26

@ronnno

Description

@ronnno

Several issues with truncatingFileWriter make it problematic in production environments:

  1. does not support size based truncation
  2. time from last truncation is initialized to the system clock on startup - so we never truncate if all runs are short
  3. loosing recent log data at the time of truncation - no file rolling
  4. Recovery from err on Truncate is 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions