BUG: Duplicate Logger Initialization in `backend/app/utils/images.py`

[Sanskriti0805]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Description
The backend/app/utils/images.py file contains duplicate logger initialization, causing the custom configured logger to be overwritten by a standard Python logger. This results in inconsistent logging behavior and loss of the project's custom logging configuration (color formatting, component prefixes, etc.).

Location
File: backend/app/utils/images.py
Lines: 23 and 29

Problem

1. Duplicate Initialization: The logger is initialized twice on lines 23 and 29
2. Overwrites Custom Logger: The second initialization uses logging.getLogger() instead of the project's get_logger(), which overwrites the properly configured logger
3. Unused Import: The logging module is imported but only used for the duplicate initialization
4. Loss of Configuration: The custom logger from get_logger() includes:
   • Color-coded log messages
   • Component-specific prefixes
   • Consistent formatting across the project
   • Environment-based configuration

Impact

• Inconsistent Logging: Logs from this module may not follow the project's logging standards
• Lost Formatting: Missing color coding and component prefixes in log output
• Code Quality: Unused import and redundant code
• Maintenance: Confusing for developers who expect consistent logging behavior

Expected Behavior
The module should use a single logger instance initialized with the project's custom get_logger() function, ensuring consistent logging behavior with proper formatting and configuration.

Solution

1. Remove the duplicate logger initialization on line 29
2. Remove the unused import logging statement
3. Keep only the correct initialization: logger = get_logger(__name__)

Steps to Reproduce

1. Check the log output from image processing operations
2. Observe that logs may not have the expected formatting/colors
3. Review the code to see duplicate logger initialization

Additional Context

• The project uses a centralized logging system via app.logging.setup_logging.get_logger()
• This function returns a properly configured logger with custom formatting
• All modules should use get_logger(__name__) instead of logging.getLogger(__name__)

Labels

• bug
• backend
• logging
• code-quality
• good-first-issue (simple fix, good for new contributors)

Priority
Low-Medium - Doesn't break functionality but affects code quality and logging consistency

Record

• I agree to follow this project's Code of Conduct

Checklist before Submitting

• Have you updated docs for it?
• Have you added unit tests?
• Have you made sure unit tests pass?
• Have you made sure code formatting is correct?
• Do Your changes passes all tests?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#548 - feat : Centralized Logging System [merged]

👤 Suggested Assignees

• Hemil36

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[Sanskriti0805]

@rahulharpal1603 i will be working on this issue , pls assign it to me

[kri-jha]

Hi 👋
I’ve submitted PR #820 which fixes the duplicate logger initialization.
Looking forward to your review. Thanks!

[Sanskriti0805]

hello @kri-jha , i Have opened the issue nd have already commented , that i will be solving it , i will be opening my own pr in a few minutes , it will be better for you to look up for new issues to solve

[Sanskriti0805]

hello @rahulharpal1603 , i have created a Pr to remove this issue which i detected please review it .

[kri-jha]

Hi @Sanskriti0805 👋
I opened the PR because the issue was not assigned at the time and was marked as a good-first-issue. There was no intention to overlap work.

@rahulharpal1603 I’ve already implemented the fix and attached PR #820 addressing the duplicate logger initialization. Kindly review it and please let me know if I can be assigned to similar issues going forward.

Thanks!

[Sanskriti0805]

Hi @kri-jha, thanks for the clarification 👍

I understand there was no ill intent, and I appreciate your contribution.

Since I opened the issue and had already commented that I would be working on it, I went ahead and submitted my own PR. In the future, it might help to check issue comments before starting work when someone has expressed intent to solve it.

@rahulharpal1603 I’ve submitted PR #821 addressing this issue as well. I’ll leave it to you to decide which PR to proceed with.

Thanks, and looking forward to contributing more!

[nishantxscooby]

I’d like to work on this issue. I’ll investigate the duplicate logger initialization in backend/app/utils/images.py and propose a fix.