Fix duplicate logger initialization in images util

[nishantxscooby]

Fixes #815

Removes duplicate logger initialization in backend/app/utils/images.py to ensure consistent logging configuration.

Summary by CodeRabbit

• Chores
  • Consolidated logging to rely on the project-level logger across utility modules.
  • Removed a redundant logger initialization to prevent duplicate log handlers and reduce noisy/duplicated log entries.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Removed a duplicate logger initialization and unused logging import from backend/app/utils/images.py, leaving the project-level get_logger(__name__) as the sole logger setup.

Changes

Cohort / File(s)	Summary
Logger initialization cleanup backend/app/utils/images.py	Deleted the redundant logging.getLogger(__name__) line and removed the unused import logging, keeping only logger = get_logger(__name__) with an explanatory comment about using the project-level logger.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I nibbled lines and found the trace,
One logger left to take its place.
No duplicate hops across the log,
Now tidy prints across the bog.
🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and clearly summarizes the main change: fixing duplicate logger initialization in the images utility file.
Linked Issues check	✅ Passed	The pull request addresses the core coding requirements from issue #815: removing duplicate logger initialization and keeping the project's custom get_logger() [#815].
Out of Scope Changes check	✅ Passed	The changes are entirely in scope—only the duplicate logger initialization was modified in images.py, aligning with the stated objective.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96dcc4d and 5a56fff.

📒 Files selected for processing (1)

• backend/app/utils/images.py

🔇 Additional comments (1)

backend/app/utils/images.py (1)

23-24: LGTM! Correct logger setup retained.

The project-level logger setup using get_logger(__name__) is correctly retained, ensuring consistent logging configuration with proper color formatting, component prefixes, and environment-based settings. The added comment helps document the rationale for future maintainers.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nishantxscooby]

I mistakenly removed the logger initialization in the previous commit. I’ve now corrected this to use only the project-level get_logger with a clarifying comment.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

backend/app/utils/images.py (1)

5-5: Remove the unused logging import.

Issue #815 explicitly requires removing the unused logging import along with the duplicate logger initialization. The logging module is not used anywhere in this file after the duplicate initialization was removed.

🔎 Proposed fix

-import logging

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96dcc4d and 5a56fff.

📒 Files selected for processing (1)

• backend/app/utils/images.py

🔇 Additional comments (1)

backend/app/utils/images.py (1)

23-24: LGTM! Correct logger setup retained.

The project-level logger setup using get_logger(__name__) is correctly retained, ensuring consistent logging configuration with proper color formatting, component prefixes, and environment-based settings. The added comment helps document the rationale for future maintainers.