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

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

Context

Roadmap item: P2 Backend - SERP cache TTL is hardcoded

The SERP result cache TTL is hardcoded to 24 hours. There is no way to adjust it without modifying source code.

What to do

  • Add SERP_CACHE_TTL_HOURS to config.py with a default of 24.
  • Update the cache logic in serp_api.py to read TTL from config.
  • Document the variable in .env.example.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=48 doubles the cache lifetime.
  • Default behavior (24 hours) is preserved when the variable is unset.
  • No hardcoded TTL value remains in serp_api.py.
## Context Roadmap item: P2 Backend - SERP cache TTL is hardcoded The SERP result cache TTL is hardcoded to 24 hours. There is no way to adjust it without modifying source code. ## What to do - Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24`. - Update the cache logic in `serp_api.py` to read TTL from config. - Document the variable in `.env.example`. ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=48` doubles the cache lifetime. - Default behavior (24 hours) is preserved when the variable is unset. - No hardcoded TTL value remains in `serp_api.py`.
AI-Manager added the P2agent-readysmallconfig labels 2026-03-30 15:23:29 +00:00
AI-Manager commented 2026-03-30 16:05:58 +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 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#1359
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?