You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cache: runtime-built tiers take no limits or jitter #1178
Found in plan 101b sweep 8b-4. packages/cli/src/runtime-cache.ts (lines ~159 and ~172) builds lruTier() and redisTier() with no options, so maxBytes/maxEntries/jitterFraction cannot be configured for the tiers the runtime builds. X_CACHE_LIMIT_INVALID and X_CACHE_JITTER_INVALID used to name app.config.ts keys that do not exist; their fixes now say "a constructor option, never an app.config.ts key", which is the truth today.
Decide: a cache section in app.config.ts read by runtime-cache.ts, or the runtime.ts override.
Thanks for the write-up — a real gap, and worth fixing.
buildTier() in packages/cli/src/runtime-cache.ts builds lruTier() and redisTier({ client }) with no options, so maxBytes/maxEntries/jitterFraction cannot reach the rungs a boot constructs — while @ultimat3/cache's LruOptions/RedisTierOptions already take them.
Logged as an enhancement; the scope follows.
🤖 Posted by developerz.ai — an automated agent, not a human.
Scoped: make the rungs the runtime builds configurable.
Where the gap is.buildTier() (packages/cli/src/runtime-cache.ts) calls lruTier() and redisTier({ client }) with no options, so maxBytes/maxEntries/jitterFraction cannot reach the tiers a boot constructs. @ultimat3/cache already takes them (LruOptions.maxBytes/jitterFraction, RedisTierOptions.maxValueBytes/jitterFraction), and X_CACHE_LIMIT_INVALID/X_CACHE_JITTER_INVALID now correctly say "a constructor option" — so the options exist and nothing reaches them.
The two paths the issue names.
Path
What it means
A cache section in app.config.ts
extend CacheConfig (today only defaultTtlMs + tiers) with per-tier limits/jitter, read by runtime-cache.ts and passed into buildTier()
The runtime.ts override
CacheTiersOptions.supplied already lets an app hand over whole CacheTiers; keep that as the only seam and document it
Work either way. The chosen key/option carries maxBytes/maxEntries/jitterFraction; buildTier() passes them through to lruTier()/redisTier(); invalid values still raise X_CACHE_LIMIT_INVALID/X_CACHE_JITTER_INVALID and their fix: names the real key; supplied keeps working with a stated precedence over config; tests pin both the pass-through and the refusals.
Open decision. Which of the two is the framework's one way is a config-surface call (axiom 1 — one way to do each thing), so it is flagged for the maintainer rather than handed to a coding agent as a coin flip.
🤖 Posted by developerz.ai — an automated agent, not a human.
Attempt 1 of 3 ended: the work ended failed with no change merged.
It has been filed again as attempt 2 of 3, carrying what the last one hit.
What stopped it:
evidence_blocked: The run recorded inaccessible evidence and stopped without shipping a change. It will not retry automatically: restore access to the recorded sources and rerun the task.
Activity
feat(sweep-8b-4): every fix line opens with what to paste or run (917…
feat(sweep-9): five app shapes gated twice, finished.ts, no planned c…
developerz-ai commentedon Nov 17, 2026
Thanks for the write-up — a real gap, and worth fixing.
buildTier()inpackages/cli/src/runtime-cache.tsbuildslruTier()andredisTier({ client })with no options, somaxBytes/maxEntries/jitterFractioncannot reach the rungs a boot constructs — while@ultimat3/cache'sLruOptions/RedisTierOptionsalready take them.Logged as an enhancement; the scope follows.
🤖 Posted by developerz.ai — an automated agent, not a human.
developerz-ai commentedon Nov 17, 2026
Scoped: make the rungs the runtime builds configurable.
Where the gap is.
buildTier()(packages/cli/src/runtime-cache.ts) callslruTier()andredisTier({ client })with no options, somaxBytes/maxEntries/jitterFractioncannot reach the tiers a boot constructs.@ultimat3/cachealready takes them (LruOptions.maxBytes/jitterFraction,RedisTierOptions.maxValueBytes/jitterFraction), andX_CACHE_LIMIT_INVALID/X_CACHE_JITTER_INVALIDnow correctly say "a constructor option" — so the options exist and nothing reaches them.The two paths the issue names.
cachesection inapp.config.tsCacheConfig(today onlydefaultTtlMs+tiers) with per-tier limits/jitter, read byruntime-cache.tsand passed intobuildTier()runtime.tsoverrideCacheTiersOptions.suppliedalready lets an app hand over wholeCacheTiers; keep that as the only seam and document itWork either way. The chosen key/option carries
maxBytes/maxEntries/jitterFraction;buildTier()passes them through tolruTier()/redisTier(); invalid values still raiseX_CACHE_LIMIT_INVALID/X_CACHE_JITTER_INVALIDand theirfix:names the real key;suppliedkeeps working with a stated precedence over config; tests pin both the pass-through and the refusals.Open decision. Which of the two is the framework's one way is a config-surface call (axiom 1 — one way to do each thing), so it is flagged for the maintainer rather than handed to a coding agent as a coin flip.
🤖 Posted by developerz.ai — an automated agent, not a human.
developerz-ai commentedon Nov 19, 2026
Let runtime-built cache tiers take limits and jitter
Stopped — this needs a human. Nothing was merged.
Reason: the run stopped on an error; its details are on the run in the developerz.ai dashboard.
1m · 12 tool calls
developerz-ai commentedon Nov 19, 2026
Attempt 1 of 3 ended: the work ended
failedwith no change merged.It has been filed again as attempt 2 of 3, carrying what the last one hit.
What stopped it:
evidence_blocked: The run recorded inaccessible evidence and stopped without shipping a change. It will not retry automatically: restore access to the recorded sources and rerun the task.developerz-ai commentedon Nov 19, 2026
Tracking pull request #1261 for this issue.