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

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

Context

Roadmap item: P2 Backend — configurable SERP cache TTL

The SERP API cache TTL is hardcoded to 24 hours. Operators have no way to tune this without modifying source code.

What to do

  1. In config.py, add SERP_CACHE_TTL_HOURS: int = 24 (read from the environment with the same name).
  2. Update the cache logic in serp_api.py to use config.SERP_CACHE_TTL_HOURS instead of the literal 24.
  3. Update .env.example to document the variable.

Acceptance criteria

  • Cache TTL is read from SERP_CACHE_TTL_HOURS env var
  • Defaults to 24 hours when unset
  • No hardcoded TTL values remain in serp_api.py
  • .env.example documents the variable
## Context Roadmap item: P2 Backend — configurable SERP cache TTL The SERP API cache TTL is hardcoded to 24 hours. Operators have no way to tune this without modifying source code. ## What to do 1. In `config.py`, add `SERP_CACHE_TTL_HOURS: int = 24` (read from the environment with the same name). 2. Update the cache logic in `serp_api.py` to use `config.SERP_CACHE_TTL_HOURS` instead of the literal `24`. 3. Update `.env.example` to document the variable. ## Acceptance criteria - [ ] Cache TTL is read from `SERP_CACHE_TTL_HOURS` env var - [ ] Defaults to 24 hours when unset - [ ] No hardcoded TTL values remain in `serp_api.py` - [ ] `.env.example` documents the variable
AI-Manager added the P2agent-readysmallconfig labels 2026-03-31 00:23:51 +00:00
AI-Manager commented 2026-03-31 01:03:53 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is already resolved. SPARC/config.py reads SERP_CACHE_TTL_HOURS from the environment (default 24 hours). Closing as complete.

[Repo Manager] This issue is already resolved. `SPARC/config.py` reads `SERP_CACHE_TTL_HOURS` from the environment (default 24 hours). Closing as complete.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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