chore: Snowflake Cortex caching follow-ups (walk-back continuation, image-block probe, cross-process cooldown)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start with the #1020 consensus review and v0.9.2 release review, then inspect the current attachMarker and cacheDisabledUntil paths. Check src/plugin/snowflake-cortex.ts and the packages/core cortexFetch PluginV2 port, and run or add the mentioned image-block unit test. Done means each deferred follow-up has a decided scope, live verification where required, and corresponding coverage or an explicit deferral.
Written by the indexing model from the issue text.
Description
Consolidated follow-ups from the #1020 consensus code review and the v0.9.2 release review. Deferred because: each needs design or live verification beyond a quick fix.
- attachMarker walk-back: when the target block already has a marker, continue scanning earlier blocks/messages for an unmarked spot to preserve a second trailing breakpoint (MiMo/GLM-5.1 finding; rare in the shipped pipeline).
- Live-probe whether Cortex honors cache_control on image blocks; add a unit test for a newly-relocated marker landing on a non-text last block.
- Cache-disable cooldown (cacheDisabledUntil) is per-process; concurrent processes each pay the probe-retry tax independently on marker-rejecting accounts (Chaos Gremlin P1). Consider shared state only if such accounts are ever observed.
- Discussion: should a (non-SyntaxError) transform bug be able to fail a chat turn, or degrade to pass-through with a loud log (Tech Lead P2)?
- Dormant paths (src/plugin/snowflake-cortex.ts, packages/core cortexFetch PluginV2 port) lack the caching fix — port it if either is revived.
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 65
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.
More from AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AltimateAI/altimate-code#1359 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
All issues in AltimateAI/altimate-code
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100