Implement opportunistic local GA fetch from prod (RFC merged)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 180
- Forks
- 137
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 21
Description
The RFC from #972 (docs/rfc/local-ga-opportunistic-fetch.md) is now merged.
Implement the phased plan described in the RFC:
- Phase 1: env vars
CRE_GA_UPSTREAM_URL/CRE_GA_NO_UPSTREAM, opportunistic fetch on cache miss - Phase 2: background pre-warming, TTL/staleness policy
- Phase 3: partial-result streaming
Ref: #534
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading docs/rfc/local-ga-opportunistic-fetch.md and the discussion in #972, then review the related context in #534. Trace the existing GA cache-miss path before implementing the three RFC phases: environment controls and opportunistic fetch, background pre-warming with TTL policy, and partial-result streaming. Done means the phased behavior is implemented and verified against the RFC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100