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

New Issue
Closed
opened 2026-03-29 01:22:39 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-29 01:22:39 +00:00
Owner
Copy Link
Copy Source

Background

The SERP cache TTL is hardcoded to 24 hours. For high-frequency or real-time use cases, operators cannot reduce it without code changes.

What to do

  1. Add SERP_CACHE_TTL_HOURS to config.py with a default of 24
  2. Update serp_api.py (or wherever the TTL is applied) to read from config
  3. Add the variable to .env.example with a comment explaining its purpose

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 results in cached SERP responses expiring after 1 hour
  • Default (24 hours) is unchanged when the variable is not set
  • Variable is documented in .env.example

References

Roadmap item: P2 Backend -- SERP cache TTL is hardcoded to 24 hours

## Background The SERP cache TTL is hardcoded to 24 hours. For high-frequency or real-time use cases, operators cannot reduce it without code changes. ## What to do 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24` 2. Update `serp_api.py` (or wherever the TTL is applied) to read from config 3. Add the variable to `.env.example` with a comment explaining its purpose ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=1` results in cached SERP responses expiring after 1 hour - Default (24 hours) is unchanged when the variable is not set - Variable is documented in `.env.example` ## References Roadmap item: P2 Backend -- SERP cache TTL is hardcoded to 24 hours
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-29 01:22:39 +00:00
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#807
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?