Add safety check to repair #32
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
westsurname
reviewed
Jul 31, 2024
|
Updated with a bunch of your proposed changes. I hope I did them all correctly. It seems to work well for me. I also included the check for Torbox, but I didn't test it since I don't use that service. |
merging latest changes
|
West added a safety check. Closing this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a check into each iteration of the outermost FOR loop to ensure that the torrent mount is up and functioning. Since the mount could get dropped at any time, I thought it best to check each time it looped since there could be significant time between each one. The command that is used can be overridden with the MOUNT_SAFETY_CHECK_COMMAND environment variable or will default to checking count > 0 for the folders within the mount.