release 1.5.0 - cron job logs testing #52
Description
the additions of the logs is very well done! I have found the following issues with the new features:
-
When you enable logging, and manually run a cron job, the live-view screen that displays shows the logs well. the issue i found was when the first job finishes, the logs and history are all in good order. but if you manually run the job again, the live-view screen displays part (or all) of the previous job log, and then proceeds to update with the logs of the current job. the previous entries scrolls by so fast I can't tell. I do suspect it is not all of the previous log since it disappears very quickly.
-
a much bigger issue is i ran a very long running job (about 1 hour), but in doing that it created a log file of 17,076KB, which was 145,003 lines in total. the cronmaster UI ran fine for a while and i could navigate around looking at the logs in the screens you added, etc. and at some point the UI locked up and showed a blank screen. after that the UI was completely unresponsive. the job still ran and completed normally, but even after the job finished the cronmaster UI was locked up. the docker console log didn't show any errors for the container. after i restarted the container, everything acted normally and i could view the log of the job that ran.