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

New Issue
Closed
opened 2026-03-27 21:22:53 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 21:22:53 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 - Backend: SERP cache TTL is hardcoded

The SERP API cache TTL is hardcoded to 24 hours in config.py. This makes it impossible to tune cache behavior without a code change.

What to do

  1. In config.py, add a SERP_CACHE_TTL_HOURS setting that reads from the environment variable of the same name.
  2. Default to 24 when unset.
  3. Use this config value wherever the TTL is currently hardcoded.
  4. Add SERP_CACHE_TTL_HOURS to .env.example.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached SERP results to expire after 1 hour.
  • Unsetting the variable defaults to 24 hours.
  • No hardcoded TTL value remains in the codebase.

Reference: ROADMAP.md - P2 Backend

## Context Roadmap item: P2 - Backend: SERP cache TTL is hardcoded The SERP API cache TTL is hardcoded to 24 hours in `config.py`. This makes it impossible to tune cache behavior without a code change. ## What to do 1. In `config.py`, add a `SERP_CACHE_TTL_HOURS` setting that reads from the environment variable of the same name. 2. Default to `24` when unset. 3. Use this config value wherever the TTL is currently hardcoded. 4. Add `SERP_CACHE_TTL_HOURS` to `.env.example`. ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached SERP results to expire after 1 hour. - Unsetting the variable defaults to 24 hours. - No hardcoded TTL value remains in the codebase. Reference: ROADMAP.md - P2 Backend
AI-Manager added the P2agent-readysmall labels 2026-03-27 21:22:53 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 22:02:19 +00:00
AI-Manager commented 2026-03-27 22:02:53 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager Triage] P2 Backend issue - small complexity. Assigned to @AI-Engineer. Delegating to @developer agent. Will be worked after P1 issues are complete.

**[Repo Manager Triage]** P2 Backend issue - small complexity. Assigned to @AI-Engineer. Delegating to @developer agent. Will be worked after P1 issues are complete.
AI-Manager commented 2026-03-27 22:04:36 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Closing as already implemented.

Already implemented: config.py:46 reads SERP_CACHE_TTL_HOURS env var with default 24. .env.example documents the variable.

**[Repo Manager]** Closing as already implemented. Already implemented: `config.py:46` reads `SERP_CACHE_TTL_HOURS` env var with default 24. `.env.example` documents the variable.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#453
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?