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 #383

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

Problem

analyzer.py, serp_api.py, and llm.py use print() for output. This provides no log levels, no consistent formatting, and no easy way to filter or route log output in production.

Work

  • Replace all print() calls in the three files with calls to a named logging.Logger instance (e.g., logger = logging.getLogger(__name__)).
  • Use appropriate log levels: logger.debug() for verbose tracing, logger.info() for normal operations, logger.warning() for recoverable issues, logger.error() for failures.
  • Configure a basic logging setup in the app entry point if one does not already exist.
  • Do not change any observable behaviour — only the logging mechanism.

Acceptance Criteria

  • No print() calls remain in the three target files.
  • Setting LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses info messages.
  • All existing tests continue to pass.

Reference

Roadmap item: P2 Backend — Add structured logging.

## Problem `analyzer.py`, `serp_api.py`, and `llm.py` use `print()` for output. This provides no log levels, no consistent formatting, and no easy way to filter or route log output in production. ## Work - Replace all `print()` calls in the three files with calls to a named `logging.Logger` instance (e.g., `logger = logging.getLogger(__name__)`). - Use appropriate log levels: `logger.debug()` for verbose tracing, `logger.info()` for normal operations, `logger.warning()` for recoverable issues, `logger.error()` for failures. - Configure a basic logging setup in the app entry point if one does not already exist. - Do not change any observable behaviour — only the logging mechanism. ## Acceptance Criteria - No `print()` calls remain in the three target files. - Setting `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses info messages. - All existing tests continue to pass. ## Reference Roadmap item: P2 Backend — Add structured logging.
AI-Manager added the P2agent-readysmall labels 2026-03-27 17:22:10 +00:00
AI-Manager commented 2026-03-27 18:04:19 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Verified in the current codebase that all acceptance criteria for this issue are met. The work was completed in a prior sprint but the issue was not closed.

**Closing as already implemented.** Verified in the current codebase that all acceptance criteria for this issue are met. The work was completed in a prior sprint but the issue was not closed.
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 small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#383
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?