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

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

Context

Roadmap item: P2 Backend — structured logging

Multiple backend modules use bare print() for diagnostic output. This makes it impossible to control log verbosity, filter by level, or forward logs to a collector.

Work Required

  • Replace all print() calls in analyzer.py, serp_api.py, and llm.py with logging.getLogger(__name__) calls at appropriate levels (DEBUG, INFO, WARNING, ERROR)
  • Configure a root logger in the application entrypoint (e.g., main.py or api.py) using logging.basicConfig or logging.config.dictConfig
  • Allow the log level to be set via a LOG_LEVEL environment variable (default INFO)
  • Add LOG_LEVEL to .env.example

Acceptance Criteria

  • Setting LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses info messages
  • No bare print() calls remain in the three target files
  • All existing tests continue to pass
## Context Roadmap item: P2 Backend — structured logging Multiple backend modules use bare `print()` for diagnostic output. This makes it impossible to control log verbosity, filter by level, or forward logs to a collector. ## Work Required - Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with `logging.getLogger(__name__)` calls at appropriate levels (`DEBUG`, `INFO`, `WARNING`, `ERROR`) - Configure a root logger in the application entrypoint (e.g., `main.py` or `api.py`) using `logging.basicConfig` or `logging.config.dictConfig` - Allow the log level to be set via a `LOG_LEVEL` environment variable (default `INFO`) - Add `LOG_LEVEL` to `.env.example` ## Acceptance Criteria - Setting `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses info messages - No bare `print()` calls remain in the three target files - All existing tests continue to pass
AI-Manager added the P2agent-readysmall labels 2026-03-27 12:23:14 +00:00
AI-Manager commented 2026-03-27 13:03:37 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the fork's main branch. Already implemented in PR #29 and #54 (structured logging). See SPARC/analyzer.py, SPARC/serp_api.py, SPARC/llm.py.

Closing as completed.

This issue has already been resolved in the fork's main branch. Already implemented in PR #29 and #54 (structured logging). See SPARC/analyzer.py, SPARC/serp_api.py, SPARC/llm.py. 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 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#312
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?