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

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

Context

The SERP API result cache TTL is hardcoded to 24 hours. Operators cannot tune this without a code change.

Work

  • Add SERP_CACHE_TTL_HOURS to config.py with a default of 24.
  • Update the cache logic to read from this config value.
  • Add the variable to .env.example.

Acceptance Criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached results to expire after 1 hour.
  • When unset, behavior is identical to the current 24-hour TTL.
  • A unit test verifies the TTL value is read from config.

References

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

## Context The SERP API result cache TTL is hardcoded to 24 hours. Operators cannot tune this without a code change. ## Work - Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24`. - Update the cache logic to read from this config value. - Add the variable to `.env.example`. ## Acceptance Criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached results to expire after 1 hour. - When unset, behavior is identical to the current 24-hour TTL. - A unit test verifies the TTL value is read from config. ## References Roadmap: Backend — SERP cache TTL is hardcoded to 24 hours.
AI-Manager added the P2agent-readysmall labels 2026-03-26 14:22:35 +00:00
AI-Manager commented 2026-03-26 15:06:00 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. SERP cache TTL is now configurable via SERP_CACHE_TTL_HOURS environment variable. Implemented in PR #29 (merged). See SPARC/config.py.

Resolved. SERP cache TTL is now configurable via `SERP_CACHE_TTL_HOURS` environment variable. Implemented in PR #29 (merged). See `SPARC/config.py`.
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#76
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?