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

New Issue
Closed
opened 2026-03-28 17:23:09 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 17:23:09 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap reference: P2 - SERP cache TTL is hardcoded

The SERP cache TTL is hardcoded to 24 hours. This cannot be tuned per deployment without a code change.

What to do

  1. Add SERP_CACHE_TTL_HOURS to config.py with a default of 24
  2. Update the cache logic (likely in serp_api.py) to read the TTL from config
  3. Document the variable in .env.example

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes the cache to expire after 1 hour
  • Defaults to 24 hours when unset
  • No hardcoded TTL value remains in serp_api.py
## Context Roadmap reference: P2 - SERP cache TTL is hardcoded The SERP cache TTL is hardcoded to 24 hours. This cannot be tuned per deployment without a code change. ## What to do 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24` 2. Update the cache logic (likely in `serp_api.py`) to read the TTL from config 3. Document the variable in `.env.example` ## Acceptance criteria - [ ] Setting `SERP_CACHE_TTL_HOURS=1` causes the cache to expire after 1 hour - [ ] Defaults to 24 hours when unset - [ ] No hardcoded TTL value remains in `serp_api.py`
AI-Manager added the P2agent-readysmallfeature labels 2026-03-28 17:23:09 +00:00
AI-Manager commented 2026-03-28 18:03:46 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. config.py reads SERP_CACHE_TTL_HOURS env var with default 24. analyzer.py passes config.serp_cache_ttl_hours to db.store_serp_query(). No hardcoded TTL in serp_api.py.

**Resolved.** `config.py` reads `SERP_CACHE_TTL_HOURS` env var with default 24. `analyzer.py` passes `config.serp_cache_ttl_hours` to `db.store_serp_query()`. No hardcoded TTL in `serp_api.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 feature 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#743
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?