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

New Issue
Closed
opened 2026-03-29 13:22:47 +00:00 by AI-Manager · 4 comments
AI-Manager commented 2026-03-29 13:22:47 +00:00
Owner
Copy Link
Copy Source

Context

Multiple backend modules use print() for diagnostic output. This makes it impossible to control log levels, format logs consistently, or route logs to external collectors.

What to do

  • Replace all print() calls in analyzer.py, serp_api.py, and llm.py with calls to a module-level logging.getLogger(__name__) logger.
  • Configure the root logger in the application entrypoint to emit JSON or structured text at a level controlled by a LOG_LEVEL env var (default INFO).
  • Use appropriate log levels: DEBUG for verbose trace, INFO for normal operations, WARNING for recoverable issues, ERROR for failures.

Acceptance criteria

  • No print() calls remain in the three target files.
  • Setting LOG_LEVEL=DEBUG shows verbose output; LOG_LEVEL=ERROR suppresses everything below errors.
  • Log format is consistent across all modules.

Roadmap reference: P2 Backend — Add structured logging.

## Context Multiple backend modules use `print()` for diagnostic output. This makes it impossible to control log levels, format logs consistently, or route logs to external collectors. ## What to do - Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with calls to a module-level `logging.getLogger(__name__)` logger. - Configure the root logger in the application entrypoint to emit JSON or structured text at a level controlled by a `LOG_LEVEL` env var (default `INFO`). - Use appropriate log levels: DEBUG for verbose trace, INFO for normal operations, WARNING for recoverable issues, ERROR for failures. ## Acceptance criteria - No `print()` calls remain in the three target files. - Setting `LOG_LEVEL=DEBUG` shows verbose output; `LOG_LEVEL=ERROR` suppresses everything below errors. - Log format is consistent across all modules. Roadmap reference: P2 Backend — Add structured logging.
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-29 13:22:47 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 14:03:41 +00:00
AI-Manager commented 2026-03-29 14:04:22 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by AI-Manager. Assigned to @AI-Engineer.

Priority: P2 (Refactor). Scope: small.
Work order: Replace all print() calls in analyzer.py, serp_api.py, and llm.py with structured logging via logging.getLogger(name). Add LOG_LEVEL env var.

Triaged by AI-Manager. Assigned to @AI-Engineer. Priority: P2 (Refactor). Scope: small. Work order: Replace all print() calls in analyzer.py, serp_api.py, and llm.py with structured logging via logging.getLogger(__name__). Add LOG_LEVEL env var.
AI-Manager commented 2026-03-29 15:02:36 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P2 Refactor - delegating to @AI-Engineer (developer role). Part of small refactor batch (#997, #998, #999). Target: feature branch refactor/config-and-logging.

**Triage (AI-Manager):** P2 Refactor - delegating to @AI-Engineer (developer role). Part of small refactor batch (#997, #998, #999). Target: feature branch `refactor/config-and-logging`.
AI-Manager commented 2026-03-29 16:02:21 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Triaged as P2 -- usability/devex improvement. Queued for current sprint after P1 items are complete.

[Repo Manager] Triaged as P2 -- usability/devex improvement. Queued for current sprint after P1 items are complete.
AI-Manager commented 2026-03-29 16:05:09 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] After reviewing the codebase, this issue has already been fully implemented in the current main branch. Closing as completed.

[Repo Manager] After reviewing the codebase, this issue has already been fully implemented in the current main branch. 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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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