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

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

Context

analyzer.py, serp_api.py, and llm.py use print() for diagnostic output. This makes log level filtering, structured log aggregation, and log formatting impossible.

Work

  • Replace all print() calls in the three files with logging.getLogger(__name__) calls at appropriate levels (DEBUG, INFO, WARNING, ERROR).
  • Configure a root logger in the application entrypoint (main.py) with a configurable log level via LOG_LEVEL env var (default INFO).
  • Use a consistent format including timestamp, level, module, and message.
  • Ensure no sensitive data (API keys, PII) is logged.

Acceptance Criteria

  • No print() calls remain in the three target files.
  • Log level is configurable via LOG_LEVEL environment variable.
  • Running the app at DEBUG level shows detailed trace; WARNING suppresses info logs.
  • CI linting (or a grep check) enforces no new print() calls.

References

Roadmap: Backend — add structured logging.

## Context `analyzer.py`, `serp_api.py`, and `llm.py` use `print()` for diagnostic output. This makes log level filtering, structured log aggregation, and log formatting impossible. ## Work - Replace all `print()` calls in the three files with `logging.getLogger(__name__)` calls at appropriate levels (`DEBUG`, `INFO`, `WARNING`, `ERROR`). - Configure a root logger in the application entrypoint (`main.py`) with a configurable log level via `LOG_LEVEL` env var (default `INFO`). - Use a consistent format including timestamp, level, module, and message. - Ensure no sensitive data (API keys, PII) is logged. ## Acceptance Criteria - No `print()` calls remain in the three target files. - Log level is configurable via `LOG_LEVEL` environment variable. - Running the app at `DEBUG` level shows detailed trace; `WARNING` suppresses info logs. - CI linting (or a grep check) enforces no new `print()` calls. ## References Roadmap: Backend — add structured logging.
AI-Manager added the P2agent-readysmall labels 2026-03-26 14:22:20 +00:00
AI-Manager commented 2026-03-26 15:05:57 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. All print() calls replaced with structured logging. Implemented across PR #29 and PR #54 (both merged). See SPARC/analyzer.py and SPARC/serp_api.py.

Resolved. All `print()` calls replaced with structured logging. Implemented across PR #29 and PR #54 (both merged). See `SPARC/analyzer.py` and `SPARC/serp_api.py`.
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#74
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?