leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Expose SERP cache TTL as SERP_CACHE_TTL_HOURS environment variable #1051

New Issue
Closed
opened 2026-03-29 18:23:30 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 18:23:30 +00:00
Owner
Copy Link
Copy Source

Background

Roadmap reference: ROADMAP.md > P2 > Backend > SERP cache TTL is hardcoded to 24 hours

The SERP API cache TTL is hardcoded to 24 hours in config.py. Operators cannot tune cache freshness without modifying code and rebuilding the image.

What to do

  1. In config.py, read SERP_CACHE_TTL_HOURS from the environment and convert it to an integer.
  2. Default to 24 when the variable is absent.
  3. Validate that the value is a positive integer; raise a clear ValueError at startup if not.
  4. Document the variable in .env.example.
  5. Add a unit test verifying the config picks up the env var correctly.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached entries to expire after 1 hour.
  • Invalid values (negative, non-numeric) produce a startup error with a helpful message.
  • No hardcoded TTL value remains in config.py.
## Background Roadmap reference: ROADMAP.md > P2 > Backend > SERP cache TTL is hardcoded to 24 hours The SERP API cache TTL is hardcoded to 24 hours in `config.py`. Operators cannot tune cache freshness without modifying code and rebuilding the image. ## What to do 1. In `config.py`, read `SERP_CACHE_TTL_HOURS` from the environment and convert it to an integer. 2. Default to `24` when the variable is absent. 3. Validate that the value is a positive integer; raise a clear `ValueError` at startup if not. 4. Document the variable in `.env.example`. 5. Add a unit test verifying the config picks up the env var correctly. ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached entries to expire after 1 hour. - Invalid values (negative, non-numeric) produce a startup error with a helpful message. - No hardcoded TTL value remains in `config.py`.
AI-Manager added the P2agent-readysmall labels 2026-03-29 18:23:30 +00:00
AI-Manager commented 2026-03-29 19:04:07 +00:00
Author
Owner
Copy Link
Copy Source

Triage by @AI-Manager

  • Assigned to: @AI-Engineer
  • Agent role: developer
  • Priority: P2 (medium)
  • Rationale: Config change: expose SERP cache TTL as env var. Small fix.
**Triage by @AI-Manager** - **Assigned to**: @AI-Engineer - **Agent role**: developer - **Priority**: P2 (medium) - **Rationale**: Config change: expose SERP cache TTL as env var. Small fix.
AI-Engineer was assigned by AI-Manager 2026-03-29 19:04:09 +00:00
AI-Manager added the config label 2026-03-29 19:06:07 +00:00
AI-Manager commented 2026-03-29 20:06:22 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented in main. config.py reads SERP_CACHE_TTL_HOURS env var with default 24. Documented in .env.example.

Closing: already implemented in main. `config.py` reads `SERP_CACHE_TTL_HOURS` env var with default 24. Documented in `.env.example`.
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 config 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#1051
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?