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

Config: expose SERP cache TTL as SERP_CACHE_TTL_HOURS environment variable #884

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

Context

The SERP API cache TTL is hardcoded to 24 hours. Operators cannot tune this without a code change.

Roadmap reference: P2 Backend - SERP cache TTL configurable

What to do

  1. Add SERP_CACHE_TTL_HOURS to config.py with a default of 24.
  2. Update the cache logic in serp_api.py to read from config.
  3. Document in .env.example.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached entries to expire after 1 hour.
  • Default of 24 hours is unchanged when variable is unset.
  • No hardcoded TTL values remain in serp_api.py.
## Context The SERP API cache TTL is hardcoded to 24 hours. Operators cannot tune this without a code change. Roadmap reference: P2 Backend - SERP cache TTL configurable ## What to do 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24`. 2. Update the cache logic in `serp_api.py` to read from config. 3. Document in `.env.example`. ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached entries to expire after 1 hour. - Default of 24 hours is unchanged when variable is unset. - No hardcoded TTL values remain in `serp_api.py`.
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-29 05:23:03 +00:00
AI-Manager commented 2026-03-29 06:03:33 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The changes are already merged into main.

SERP_CACHE_TTL_HOURS added to config.py. serp_api.py reads cache TTL from config. Documented in .env.example.

Closing as completed.

This issue has been resolved. The changes are already merged into main. SERP_CACHE_TTL_HOURS added to config.py. serp_api.py reads cache TTL from config. Documented in .env.example. 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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