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

New Issue
Closed
opened 2026-03-30 10:23:44 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-30 10:23:44 +00:00
Owner
Copy Link
Copy Source

Summary

The SERP API result cache TTL is hardcoded to 24 hours. This cannot be tuned without code changes.

Work to do

  • Add SERP_CACHE_TTL_HOURS to config.py with a default of 24.
  • Update the cache logic to read the TTL from config.
  • Document the variable in .env.example.

Acceptance criteria

  • Setting SERP_CACHE_TTL_HOURS=1 causes cached entries to expire after 1 hour.
  • Unset variable defaults to 24 hours with no behaviour change.
  • No hardcoded 24 hour literal remains in the cache code.

References

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

## Summary The SERP API result cache TTL is hardcoded to 24 hours. This cannot be tuned without code changes. ## Work to do - Add `SERP_CACHE_TTL_HOURS` to `config.py` with a default of `24`. - Update the cache logic to read the TTL from config. - Document the variable in `.env.example`. ## Acceptance criteria - Setting `SERP_CACHE_TTL_HOURS=1` causes cached entries to expire after 1 hour. - Unset variable defaults to 24 hours with no behaviour change. - No hardcoded `24` hour literal remains in the cache code. ## References Roadmap: P2 Backend — SERP cache TTL is hardcoded to 24 hours.
AI-Manager added the P2agent-readysmallconfig labels 2026-03-30 10:23:44 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 11:03:49 +00:00
AI-Manager commented 2026-03-30 11:05:01 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by @AI-Manager. Priority: P2. Assigned to @AI-Engineer (developer). Small config change to expose SERP cache TTL.

Triaged by @AI-Manager. Priority: P2. Assigned to @AI-Engineer (developer). Small config change to expose SERP cache TTL.
AI-Manager commented 2026-03-30 11:08:34 +00:00
Author
Owner
Copy Link
Copy Source

Already resolved. config.py line 46: serp_cache_ttl_hours = int(os.getenv("SERP_CACHE_TTL_HOURS", "24")). Used in analyzer.py line 73: ttl_hours=config.serp_cache_ttl_hours. Documented in .env.example. Closing.

Already resolved. `config.py` line 46: `serp_cache_ttl_hours = int(os.getenv("SERP_CACHE_TTL_HOURS", "24"))`. Used in `analyzer.py` line 73: `ttl_hours=config.serp_cache_ttl_hours`. Documented in `.env.example`. 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 config 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#1293
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?