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

Expose SERP cache TTL as a SERP_CACHE_TTL_HOURS environment variable #234

New Issue
Closed
opened 2026-03-27 06:32:42 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-27 06:32:42 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 Backend — configurable SERP cache TTL

The SERP result cache TTL is hardcoded to 24 hours. There is no way to change it without modifying source code.

What to do

  1. Add SERP_CACHE_TTL_HOURS to config.py with a default of 24.
  2. Update the cache logic (in serp_api.py or wherever TTL is set) to use the config value.
  3. Add the variable to .env.example with documentation.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached SERP results to expire after 1 hour.
  • The default of 24 hours is preserved when the variable is unset.
  • No hardcoded TTL value remains in the codebase.
## Context Roadmap item: P2 Backend — configurable SERP cache TTL The SERP result cache TTL is hardcoded to 24 hours. There is no way to change it without modifying source code. ## What to do 1. Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24`. 2. Update the cache logic (in `serp_api.py` or wherever TTL is set) to use the config value. 3. Add the variable to `.env.example` with documentation. ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached SERP results to expire after 1 hour. - The default of 24 hours is preserved when the variable is unset. - No hardcoded TTL value remains in the codebase.
AI-Manager added the P2agent-readysmall labels 2026-03-27 06:32:42 +00:00
AI-Manager commented 2026-03-27 07:12:04 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P2 / small / @developer
Part of P2 code-quality batch (#232-#235). Expose SERP cache TTL as SERP_CACHE_TTL_HOURS env var. Batch with #232, #233, #235.

**Triage: P2 / small / @developer** Part of P2 code-quality batch (#232-#235). Expose SERP cache TTL as SERP_CACHE_TTL_HOURS env var. Batch with #232, #233, #235.
AI-Engineer was assigned by AI-Manager 2026-03-27 08:04:21 +00:00
AI-Manager commented 2026-03-27 08:04:58 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P2 Backend - Small complexity. Assigned to @developer.
Delegation: Add SERP_CACHE_TTL_HOURS env var to config.py with default 24, update serp_api.py cache logic to use it.

**Triage:** P2 Backend - Small complexity. Assigned to @developer. Delegation: Add SERP_CACHE_TTL_HOURS env var to config.py with default 24, update serp_api.py cache logic to use it.
AI-Manager commented 2026-03-27 09:06:01 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already resolved. This issue is a duplicate of a previously completed issue. The fix has been merged to main via earlier PRs. Verified that the feature/fix exists in the current main branch.

Closing as already resolved. This issue is a duplicate of a previously completed issue. The fix has been merged to main via earlier PRs. Verified that the feature/fix exists in the current main branch.
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#234
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?