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

Feature: Expose SERP cache TTL as SERP_CACHE_TTL_HOURS environment variable #718

New Issue
Closed
opened 2026-03-28 16:22:51 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 16:22:51 +00:00
Owner
Copy Link
Copy Source

Summary

The SERP API cache TTL is hardcoded to 24 hours in config.py. Operators cannot tune cache freshness without modifying source code.

What to do

  • Add SERP_CACHE_TTL_HOURS to config.py (default 24).
  • Update the cache logic in serp_api.py (or wherever TTL is applied) to read from config.
  • Document the variable in .env.example.

Acceptance Criteria

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

Reference

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

## Summary The SERP API cache TTL is hardcoded to 24 hours in `config.py`. Operators cannot tune cache freshness without modifying source code. ## What to do - Add `SERP_CACHE_TTL_HOURS` to `config.py` (default `24`). - Update the cache logic in `serp_api.py` (or wherever TTL is applied) to read from config. - Document the variable in `.env.example`. ## Acceptance Criteria - [ ] Setting `SERP_CACHE_TTL_HOURS=1` causes cached results to expire after 1 hour. - [ ] Unsetting the variable defaults to 24 hours. - [ ] No hardcoded TTL value remains in the codebase. ## Reference Roadmap: P2 Backend — SERP cache TTL is hardcoded to 24 hours.
AI-Manager added the P2agent-readysmallfeature labels 2026-03-28 16:22:51 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 17:03:07 +00:00
AI-Manager commented 2026-03-28 17:05:53 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Already resolved. SERP_CACHE_TTL_HOURS env var in config.py, used in analyzer.py SERP cache logic.

Closing as already implemented in the codebase.

[Repo Manager] Already resolved. SERP_CACHE_TTL_HOURS env var in config.py, used in analyzer.py SERP cache logic. Closing as already implemented in the codebase.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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