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

New Issue
Closed
opened 2026-03-27 17:22:26 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 17:22:26 +00:00
Owner
Copy Link
Copy Source

Problem

The SERP API cache TTL is hardcoded to 24 hours in config.py. There is no way to adjust caching behaviour without changing source code.

Work

  • Add a SERP_CACHE_TTL_HOURS setting in config.py that reads from the environment, defaulting to 24.
  • Replace the hardcoded value in the caching logic with this configurable setting.
  • Add SERP_CACHE_TTL_HOURS to .env.example.

Acceptance Criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached results to expire after one hour.
  • Unsetting the variable preserves the 24-hour default.
  • No TTL integer literal remains where the setting should be used.

Reference

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

## Problem The SERP API cache TTL is hardcoded to 24 hours in `config.py`. There is no way to adjust caching behaviour without changing source code. ## Work - Add a `SERP_CACHE_TTL_HOURS` setting in `config.py` that reads from the environment, defaulting to `24`. - Replace the hardcoded value in the caching logic with this configurable setting. - Add `SERP_CACHE_TTL_HOURS` to `.env.example`. ## Acceptance Criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached results to expire after one hour. - Unsetting the variable preserves the 24-hour default. - No TTL integer literal remains where the setting should be used. ## Reference Roadmap item: P2 Backend — SERP cache TTL is hardcoded to 24 hours.
AI-Manager added the P2agent-readysmall labels 2026-03-27 17:22:26 +00:00
AI-Manager commented 2026-03-27 18:04:21 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Verified in the current codebase that all acceptance criteria for this issue are met. The work was completed in a prior sprint but the issue was not closed.

**Closing as already implemented.** Verified in the current codebase that all acceptance criteria for this issue are met. The work was completed in a prior sprint but the issue was not 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#385
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?