fix: remove duplicate logger initialization in images.py

[Rudra-Tiwari-codes]

Summary

Fixes #815

Removes duplicate logger initialization in backend/app/utils/images.py that was causing the custom configured logger to be overwritten by a standard Python logger.

Changes Made

• Removed duplicate logger = logging.getLogger(__name__) on line 29
• Removed unused import logging statement
• Kept the correct initialization: logger = get_logger(__name__)

Summary by CodeRabbit

• Refactor
  • Improved internal code organization to enhance maintainability.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The change removes duplicate logger initialization from backend/app/utils/images.py by eliminating the redundant logging import and the standard logging.getLogger(__name__) call, retaining only the project's custom get_logger(__name__) logger for consistent logging behavior.

Changes

Cohort / File(s)	Change Summary
Logger Cleanup backend/app/utils/images.py	Removed unused import logging statement and redundant logger = logging.getLogger(__name__) initialization; retained project's custom get_logger(__name__) for consistent logging configuration

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A logger once doubled in sight,
Causing confusion and logging blight,
One duplicate gone, one remains,
Now logs flow clean through the veins!
Custom colors shine bright and right! 🎨✨

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 concisely describes the main change: removing duplicate logger initialization from images.py file.
Linked Issues check	✅ Passed	The PR successfully addresses all coding requirements from issue #815: removes duplicate logger initialization on line 29, removes unused logging import, and retains get_logger(name) initialization.
Out of Scope Changes check	✅ Passed	All changes are directly related to the linked issue #815. The modifications are limited to removing the duplicate logger initialization and unused import as specified.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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 81286fa and 78b292a.

📒 Files selected for processing (1)

• backend/app/utils/images.py

💤 Files with no reviewable changes (1)

• backend/app/utils/images.py

---

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.}

[fransafu]

Warning: This author is forking multiple ML projects such as google-deepmind/alphafold, ml-explore/mlx, openai/CLIP, pytorch/pytorch, tensorflow/tensorflow, anthropics/claude-code, vllm-project/vllm, and others, adding minimal "contributions" (often for tests or miscellaneous changes) without proper validation. A review of their commits shows mostly local implementations of TODOs copied from existing projects, with little to no substantive review or testing.

So far, this author has forked 41 repositories following the same pattern. Be careful when accepting this PR. It’s also concerning how this author is able to submit PRs across four repositories in the same day, each requiring large context, which strongly suggests a highly automated workflow.

[Rudra-Tiwari-codes]

Thank you for the feedback regarding my recent activity. I am a student and I have been using these smaller tasks as a way to familiarize myself with the architecture of various codebases. I was not aware that submitting multiple minor pull requests was considered disruptive to the maintainer workflow or seen as contribution padding. I appreciate the correction and will pay much closer attention to the impact of my work moving forward. I am closing this pull request now to focus on delivering more substantive technical contributions that provide genuine value to the community.