All logs from the current patch-hub execution should be written to a specific file. The file should retain its current logs until another patch-hub execution begins. Additionally, the current behavior of saving each execution log in a separate file to preserve log history should remain unchanged.
Motivation:
Currently, for each patch-hub run, we save a separate log file. This is great for preserving the log history of old runs but not ideal for debugging patch-hub in real-time. A simple solution to make debugging easier would be to have an additional log file with a fixed path, like latest.log. This file would always contain the logs of the current patch-hub run, allowing developers to open another terminal and use a command like watch -n 0.5 -d cat latest.log to see the logs as they are generated.
Description:
All logs from the current patch-hub execution should be written to a specific file. The file should retain its current logs until another patch-hub execution begins. Additionally, the current behavior of saving each execution log in a separate file to preserve log history should remain unchanged.
Motivation:
Currently, for each patch-hub run, we save a separate log file. This is great for preserving the log history of old runs but not ideal for debugging patch-hub in real-time. A simple solution to make debugging easier would be to have an additional log file with a fixed path, like latest.log. This file would always contain the logs of the current patch-hub run, allowing developers to open another terminal and use a command like
watch -n 0.5 -d cat latest.logto see the logs as they are generated.