Is there a way to suppress the same error from being logged multiple times in the output_log.txt, or a way to cap the log file size? Even when the log file clears upon startup, we are a bit worried about the file size growing indefinitely for any potential repeat per-update kind of bug which we may have missed in our deployed build, as it might grow the log size to problematically large sizes for the disk. Thanks!
↧