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
Is your feature request related to a problem? Please describe.
Suggested by @stinney. Over time, the log file can get very long, which makes it much harder to look through it for debugging.
Describe the solution you'd like
Various possibilities:
When writing to the log, check its age or size and delete/truncate if over a certain threshold.
Add a command to clear the log (and add a suggestion to do so in the documentation for reporting problems)
Suggest to users that they delete the file before retrying a command and sharing the log.
Describe alternatives you've considered
See above. Or perhaps our logging configuration already takes care of that?
So the threshold size is 20000000 bytes (~ 19 MiB). Concretely, is the suggestion to reduce the threshold? For example, my log file has currently 324 KiB (in 6352 lines), so filling up 19 MiB will take quite some more time, but I don't think we want to spread the log over several small files (say, less than 1 MiB).
Since we already rotate the file (I had forgotten!), I think this is fine. Have added a note in #12 to allow customising the maximum log size we retain.
Is your feature request related to a problem? Please describe.
Suggested by @stinney. Over time, the log file can get very long, which makes it much harder to look through it for debugging.
Describe the solution you'd like
Various possibilities:
Describe alternatives you've considered
See above. Or perhaps our logging configuration already takes care of that?
Additional context
If we want to rotate the log file, there is an option to limit how many old files are kept.
The text was updated successfully, but these errors were encountered: