Cached supplemental draws reuse the primary Stage 7 result
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 63/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- ai-infra-agents
Research direction
Start with src/pipeline/lens-runner.ts at lines 309 and 532, then trace the cache key in src/llm/pi-runner.ts around line 1380. Reproduce the reported case: cache on yields one provider call for the primary and supplemental draws, while cache off yields two. Done when retained supplemental modes make the second draw call the provider and the existing cache behavior is covered by a focused test.
Written by the indexing model from the issue text.
Description
Problem: With cache enabled and one deep packet, K=2 at concurrency one reports two supplemental passes but calls the provider once, reusing the primary draw. Scope any fix to retained supplemental modes.
File:line: src/pipeline/lens-runner.ts:309,532; src/llm/pi-runner.ts:1380.
Evidence: Production scheduler and Pi runner with scripted adapter verified a cache write/hit versus two provider calls with cache off; @architect confirmed the cache key. Related existing issue: #30.
Suggested fix size: M.
Found during #44 (workstream C, challenged by @architect).
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 1
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from 0xPolygon/codegenie
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
All issues in 0xPolygon/codegenie
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day