Improve error handling to prevent blocking and log errors

[maxgreco]

Description:
The purpose of this pull request is to enhance the error handling in TagGUI to prevent the program from being blocked by errors while still logging them for debugging purposes. By implementing these changes, TagGUI will become more resilient and user-friendly, as it will continue executing even if errors occur, and the errors will be logged for further investigation.

Proposed Changes:

1. Use try/except blocks around code sections that may raise exceptions to catch and handle errors gracefully. For example:

try:
    # Code that may raise an exception
except Exception as e:
    # Log the error
    logger.error(f"An error occurred: {str(e)}")
    # Continue execution

2. Configure a logger to record errors to a file instead of just displaying them on the console. Use Python's logging module:

import logging

# Configure the logger
logging.basicConfig(filename='taggui.log', level=logging.ERROR, 
                    format='%(asctime)s %(levelname)s: %(message)s')
logger = logging.getLogger(__name__)

3. In critical parts of the program flow, such as loops that process images, use a more generic try/except block to prevent an error on one image from blocking the entire process:

for image in images:
    try:
        # Process the image
    except:
        # Log the error and move on to the next image
        logger.error(f"Error processing {image}")
        continue

4. In functions that interact with external services (e.g., ML models) or read/write files, handle specific expected exceptions (e.g., connection errors, missing files) and use a catch-all generic block for unexpected errors.

5. In callbacks related to the user interface, display user-friendly error messages in dialogs or the status bar without interrupting the program.

By implementing these changes, TagGUI will become more robust and user-friendly. Errors will be caught, logged, and handled gracefully, allowing the program to continue executing while still keeping track of any issues that arise.

Please let me know if you have any questions or suggestions regarding these proposed changes.

[jhc13]

Is there a specific error you encountered? There already exist try-except blocks around parts of the code that need them.

[maxgreco]

Thank you for your response, I've resolved using Bad Peggy to detect corrupted images in my 15 tb collection, 2k images were corrupted, I've deleted them and now TagGui is working flawlessly -> https://www.majorgeeks.com/files/details/bad_peggy.html