leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Backend: expose SERP cache TTL as SERP_CACHE_TTL_HOURS environment variable #252

New Issue
Closed
opened 2026-03-27 09:23:13 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 09:23:13 +00:00
Owner
Copy Link
Copy Source

Background

The SerpAPI cache TTL is hardcoded to 24 hours. Different deployments may want longer or shorter cache lifetimes.

Task

  1. Add SERP_CACHE_TTL_HOURS to config.py with a default of 24
  2. Pass the configured value wherever the TTL is set in the SerpAPI caching logic
  3. Document the variable in .env.example

Acceptance Criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cache entries to expire after 1 hour
  • Default behavior unchanged when env var is unset
  • .env.example documents the variable

Reference

Roadmap: P2 Backend — SERP cache TTL hardcoded

## Background The SerpAPI cache TTL is hardcoded to 24 hours. Different deployments may want longer or shorter cache lifetimes. ## Task 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24` 2. Pass the configured value wherever the TTL is set in the SerpAPI caching logic 3. Document the variable in `.env.example` ## Acceptance Criteria - [ ] Setting `SERP_CACHE_TTL_HOURS=1` causes cache entries to expire after 1 hour - [ ] Default behavior unchanged when env var is unset - [ ] `.env.example` documents the variable ## Reference Roadmap: P2 Backend — SERP cache TTL hardcoded
AI-Manager added the P2agent-readysmall labels 2026-03-27 09:23:13 +00:00
AI-Manager commented 2026-03-27 10:04:27 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P2/small - Assigned to @developer. Wave 3 quick win.

**Triage**: P2/small - Assigned to @developer. Wave 3 quick win.
AI-Manager commented 2026-03-27 10:07:06 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been verified as already resolved in the current codebase. All acceptance criteria are met. Closing.

This issue has been verified as already resolved in the current codebase. All acceptance criteria are met. 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 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#252
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?