leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Replace print() calls with structured logging in analyzer.py, serp_api.py, and llm.py #339

New Issue
Closed
opened 2026-03-27 14:22:15 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 14:22:15 +00:00
Owner
Copy Link
Copy Source

Problem

Multiple backend modules use bare print() calls for diagnostic output. This prevents log level filtering, consistent formatting, and integration with log aggregation systems.

Work

  • Add a logging configuration in a shared logger.py or in config.py (log level from LOG_LEVEL env var, defaulting to INFO).
  • Replace all print() calls in analyzer.py, serp_api.py, and llm.py with logger.info() / logger.warning() / logger.error() as appropriate.
  • Use structured log messages (include relevant context like patent ID, company name, model name).
  • Ensure the FastAPI app configures uvicorn logging to use the same handler.

Acceptance Criteria

  • No print() calls remain in the three listed files.
  • Setting LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses info messages.
  • Existing tests still pass.

Reference

Roadmap item: P2 Backend — Add structured logging.

## Problem Multiple backend modules use bare `print()` calls for diagnostic output. This prevents log level filtering, consistent formatting, and integration with log aggregation systems. ## Work - Add a `logging` configuration in a shared `logger.py` or in `config.py` (log level from `LOG_LEVEL` env var, defaulting to `INFO`). - Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with `logger.info()` / `logger.warning()` / `logger.error()` as appropriate. - Use structured log messages (include relevant context like patent ID, company name, model name). - Ensure the FastAPI app configures `uvicorn` logging to use the same handler. ## Acceptance Criteria - No `print()` calls remain in the three listed files. - Setting `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses info messages. - Existing tests still pass. ## Reference Roadmap item: P2 Backend — Add structured logging.
AI-Manager added the P2agent-readymedium labels 2026-03-27 14:22:15 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 15:02:45 +00:00
AI-Manager commented 2026-03-27 15:05:25 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is resolved. All three files (analyzer.py, serp_api.py, llm.py) use logging.getLogger(name) with no remaining print() calls. config.py configures LOG_LEVEL from environment.

[Repo Manager] This issue is resolved. All three files (analyzer.py, serp_api.py, llm.py) use logging.getLogger(__name__) with no remaining print() calls. config.py configures LOG_LEVEL from environment.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#339
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?