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

Replace print() calls with structured Python logging #805

New Issue
Closed
opened 2026-03-29 01:22:25 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 01:22:25 +00:00
Owner
Copy Link
Copy Source

Background

analyzer.py, serp_api.py, and llm.py use print() for debug output. This makes it impossible to control log levels, redirect output, or parse logs in production.

What to do

  1. Add a logging configuration module (or configure in config.py) that sets format, level, and handlers
  2. Replace every print() in analyzer.py, serp_api.py, and llm.py with appropriate logging.debug/info/warning/error calls
  3. Expose a LOG_LEVEL environment variable (default: INFO)
  4. Ensure log output includes timestamp, logger name, and level

Acceptance criteria

  • No print() calls remain in the three target files
  • Setting LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses info logs
  • Log lines include structured fields (timestamp, level, logger)
  • Existing tests still pass

References

Roadmap item: P2 Backend -- Add structured logging

## Background `analyzer.py`, `serp_api.py`, and `llm.py` use `print()` for debug output. This makes it impossible to control log levels, redirect output, or parse logs in production. ## What to do 1. Add a logging configuration module (or configure in `config.py`) that sets format, level, and handlers 2. Replace every `print()` in `analyzer.py`, `serp_api.py`, and `llm.py` with appropriate `logging.debug/info/warning/error` calls 3. Expose a `LOG_LEVEL` environment variable (default: `INFO`) 4. Ensure log output includes timestamp, logger name, and level ## Acceptance criteria - No `print()` calls remain in the three target files - Setting `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses info logs - Log lines include structured fields (timestamp, level, logger) - Existing tests still pass ## References Roadmap item: P2 Backend -- Add structured logging
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-29 01:22:25 +00:00
AI-Manager commented 2026-03-29 02:04:35 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #29 (feat: configurable LLM model, SERP cache TTL, structured logging, fix type). Closing as completed.

This issue has already been resolved and merged into main via PR #29 (feat: configurable LLM model, SERP cache TTL, structured logging, fix type). Closing as completed.
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 refactor 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#805
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?