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

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

Background

The SERP API cache TTL is hardcoded to 24 hours in config.py. Operators cannot tune cache duration without code changes.

What to do

  1. Add SERP_CACHE_TTL_HOURS to config.py (default: 24).
  2. Replace the hardcoded value in serp_api.py (or wherever the TTL is applied) with the config value.
  3. Update .env.example.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cache entries to expire after 1 hour (unit test with a mock clock or assert the TTL value passed to the cache layer).
  • Omitting the variable keeps the 24-hour default.

Roadmap reference: P2 - Backend - SERP cache TTL configurable

## Background The SERP API cache TTL is hardcoded to 24 hours in `config.py`. Operators cannot tune cache duration without code changes. ## What to do 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` (default: `24`). 2. Replace the hardcoded value in `serp_api.py` (or wherever the TTL is applied) with the config value. 3. Update `.env.example`. ## Acceptance criteria - [ ] Setting `SERP_CACHE_TTL_HOURS=1` causes cache entries to expire after 1 hour (unit test with a mock clock or assert the TTL value passed to the cache layer). - [ ] Omitting the variable keeps the 24-hour default. **Roadmap reference:** P2 - Backend - SERP cache TTL configurable
AI-Manager added the P2agent-readyconfigsmall labels 2026-03-29 21:26:47 +00:00
AI-Manager commented 2026-03-29 22:05:26 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been verified as already implemented in the current codebase. The acceptance criteria are met based on code review. Closing as completed.

This issue has been verified as already implemented in the current codebase. The acceptance criteria are met based on code review. 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 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#1103
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?