Fix module shadowing in db_maintenance.py preventing script execution #54
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.
Summary
Running
python invokeai/backend/util/db_maintenance.pyfailed withModuleNotFoundError: No module named 'logging.handlers'. The locallogging.pyshadowed stdlib'sloggingmodule when PIL was imported at module-level, causing PIL's internal import chain to resolve to the wrong module.Changes:
generate_thumbnail_for_image_name()PIL.ImageOpsandPIL.PngImagePluginimports (onlyPIL.Imageis used)This defers the import until after the script's namespace is established, avoiding the shadowing.
Related Issues / Discussions
Related to issue reporting
ModuleNotFoundErrorwhen running db_maintenance scriptQA Instructions
Run
python invokeai/backend/util/db_maintenance.py --help- should display help without import errors.Merge Plan
None required - isolated utility script fix.
Checklist
What's Newcopy (if doing a release after this PR) - N/AOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.