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

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

Background

Multiple backend modules use print() for diagnostics. This makes it impossible to control log verbosity, route logs to structured sinks, or filter by severity in production.

Task

  1. Replace all print() calls in analyzer.py, serp_api.py, and llm.py with calls to a module-level logging.getLogger(__name__) logger.
  2. Use appropriate log levels (DEBUG, INFO, WARNING, ERROR).
  3. Configure root logging format in the app entrypoint (e.g. JSON format for production, human-readable for development).

Acceptance Criteria

  • No print() calls remain in analyzer.py, serp_api.py, or llm.py.
  • Log level is controllable via the LOG_LEVEL environment variable.
  • Existing tests still pass.

Reference

Roadmap: P2 Backend -- Add structured logging.

## Background Multiple backend modules use `print()` for diagnostics. This makes it impossible to control log verbosity, route logs to structured sinks, or filter by severity in production. ## Task 1. Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with calls to a module-level `logging.getLogger(__name__)` logger. 2. Use appropriate log levels (`DEBUG`, `INFO`, `WARNING`, `ERROR`). 3. Configure root logging format in the app entrypoint (e.g. JSON format for production, human-readable for development). ## Acceptance Criteria - [ ] No `print()` calls remain in `analyzer.py`, `serp_api.py`, or `llm.py`. - [ ] Log level is controllable via the `LOG_LEVEL` environment variable. - [ ] Existing tests still pass. ## Reference Roadmap: P2 Backend -- Add structured logging.
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-29 09:23:03 +00:00
AI-Manager commented 2026-03-29 10:04:21 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved. All print() calls have been replaced with structured logging in analyzer.py, serp_api.py, and llm.py -- grep confirms zero remaining print() calls in those files. config.py configures the logging format and level via LOG_LEVEL env var. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved. All `print()` calls have been replaced with structured `logging` in `analyzer.py`, `serp_api.py`, and `llm.py` -- grep confirms zero remaining `print()` calls in those files. `config.py` configures the logging format and level via `LOG_LEVEL` env var. Closing as already implemented.
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#947
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?