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
Step 1. Create .env file with report set as mode
Step 2. Attempt to override mode with shell command python plex_image_cleanup.py -m remove or --mode remove (any other mode as well) as well as any other possible option shell command. None work.
Step 3. Script will not run, no error occurs, powershell just waits for next input
Issue 2: Log file block
Step 1. Run a report mode session and it creates a log file
Step 2. Attempt to run another session, script will not run, powershell waits for next command
Step 3. Delete log file, script can then run again.
I've tried setting both Trace Logs and Log Requests to True, still no difference.
Folder is located C:\Users\USER\ImageMaid-1.0.2 - have permissions.
I can confirm that this issue also occurs on the latest release - v1.1.1. Have to go and manually delete or rename the log file every time before I run the script. I was quite bewildered why the script immediately exited after the first run.
Version Number
ImageMaid-1.0.2
What branch are you on?
master
Describe the Bug
Step 1. Create .env file with report set as mode
Step 2. Attempt to override mode with shell command
python plex_image_cleanup.py -m remove
or--mode remove
(any other mode as well) as well as any other possible option shell command. None work.Step 3. Script will not run, no error occurs, powershell just waits for next input
Issue 2: Log file block
Step 1. Run a report mode session and it creates a log file
Step 2. Attempt to run another session, script will not run, powershell waits for next command
Step 3. Delete log file, script can then run again.
I've tried setting both Trace Logs and Log Requests to True, still no difference.
Folder is located C:\Users\USER\ImageMaid-1.0.2 - have permissions.
Logs and screenshot attached
Logs
https://gist.github.com/tylerreed19/89b6d3d5d5d1ea70b98ef8da48cbd3ec
The text was updated successfully, but these errors were encountered: