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
Recovery files tend to build up rapidly over time, currently the user has to periodically clean these out by themselves. A better solution would be either of:
Only keep a small number (say the last week)
Provide a command-line flag such as --recovery-clean and just wipe out anything in the directory with it.
Rearrange how the file is handled within the code. Use the global jobfile parameter simply for initial creation. Then store a handle to the file under each job (no other place to put it). This way can make use of the filename throughout Longbow, no need to create new recovery file on recovery or reconnections and can add code to the cleanup function to kill the recovery file once all jobs are done.
The text was updated successfully, but these errors were encountered:
Preparations for adding the cleanup code. This involved making the
recovery file name accessable outside of the scheduling module.
To accomplish this, the "recoveryfile" parameter was added to the
default data structure "jobs" this is initialised during the
configuration steps of Longbow. Unit tests were updated and some new
tests added to retain coverage and test new functionality.
Recovery files tend to build up rapidly over time, currently the user has to periodically clean these out by themselves. A better solution would be either of:
The text was updated successfully, but these errors were encountered: