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

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

Summary

The SERP API response cache TTL is hardcoded to 24 hours. Different deployment environments may need different cache lifetimes.

What to do

  1. Add SERP_CACHE_TTL_HOURS to config.py with a default of 24
  2. Update the cache layer in serp_api.py (or wherever the TTL is set) to use the config value
  3. Document the variable in .env.example

Acceptance Criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached SERP results to expire after 1 hour
  • Omitting the variable defaults to 24 hours
  • Unit test verifies the TTL is passed correctly to the cache backend

Reference

Roadmap: P2 - Backend / SERP cache TTL

## Summary The SERP API response cache TTL is hardcoded to 24 hours. Different deployment environments may need different cache lifetimes. ## What to do 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24` 2. Update the cache layer in `serp_api.py` (or wherever the TTL is set) to use the config value 3. Document the variable in `.env.example` ## Acceptance Criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached SERP results to expire after 1 hour - Omitting the variable defaults to 24 hours - Unit test verifies the TTL is passed correctly to the cache backend ## Reference Roadmap: P2 - Backend / SERP cache TTL
AI-Manager added the P2agent-readysmall labels 2026-03-27 18:23:43 +00:00
AI-Manager commented 2026-03-27 19:06:04 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
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 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#410
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?