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

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

Context

Roadmap item: P2 Backend - Add structured logging

Multiple backend modules use print() for logging. This makes it impossible to filter by log level or integrate with log aggregation systems.

What to do

  • Replace all print() calls in analyzer.py, serp_api.py, and llm.py with Python logging module calls at appropriate levels (DEBUG, INFO, WARNING, ERROR).
  • Configure a root logger in the application entrypoint with a consistent format (e.g., JSON or structured text).
  • Expose a LOG_LEVEL environment variable defaulting to INFO.

Acceptance criteria

  • No print() calls remain in the three target files.
  • Log output respects the LOG_LEVEL environment variable.
  • Running the app produces structured log output.
## Context Roadmap item: P2 Backend - Add structured logging Multiple backend modules use `print()` for logging. This makes it impossible to filter by log level or integrate with log aggregation systems. ## What to do - Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with Python `logging` module calls at appropriate levels (DEBUG, INFO, WARNING, ERROR). - Configure a root logger in the application entrypoint with a consistent format (e.g., JSON or structured text). - Expose a `LOG_LEVEL` environment variable defaulting to `INFO`. ## Acceptance criteria - No `print()` calls remain in the three target files. - Log output respects the `LOG_LEVEL` environment variable. - Running the app produces structured log output.
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-30 15:23:10 +00:00
AI-Manager commented 2026-03-30 16:06:02 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.
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#1357
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?