Trace: extract and replace pasted images in Pi transcripts
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by reading the Pi spec-source pointer tracker dependency (#3704) and the design reference (#3569), then locate trace.PastedImageFinder and the spec-copy replacement path. Add regressions for finder, replacer, action, and malformed input, and run the repeated-image live scenario. Done means the measured scenario stores one material, removes supported inline duplicates only after storage succeeds, and the compatibility matrix reflects the result.
由索引模型根據 Issue 內容生成。
描述
Problem
The compatibility matrix marks Pi pasted-image pointers as No. User-pasted image data remains inline in the Pi transcript instead of being stored once as a spec material and replaced with a pointer.
Scope
Implement Pi's trace.PastedImageFinder and extend its spec-copy replacement path for the native image block shapes that Pi persists.
Acceptance criteria
- Extract valid user-pasted image data from supported Pi message blocks.
- Deduplicate decoded bytes and assign deterministic
Pasted image Nordering. - Exclude tool-result images and non-paste image records.
- Replace inline copies only after the material is stored successfully.
- Keep invalid data, remote URLs, path-only records, and storage failures inline without blocking push.
- Reuse an already captured identical image instead of creating a duplicate material.
- Add finder, replacer, action, and malformed-input regressions.
- Run the repeated-image live scenario and verify one stored material and no supported inline duplicate.
- Update the compatibility matrix from measured results.
Non-goals
- Treating tool-result images as user pastes.
- Fetching remote image URLs.
Dependencies
- Pi spec-source pointer tracker, because this extends the same provider replacement path.
- Design reference: #3569.
- Baseline Pi support: #3704.
- 主要語言
- Go
- 星號
- 582
- 分支
- 61
- 平均合併
- 12 小時 47 分鐘
- 30 天內合併 PR
- 137
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
chainloop-dev/chainloop 的其他 Issue
-
feature-parity trace-provider
難度 2/5 1-3 小時 新手友好度 70/100
chainloop-dev/chainloop#3802 ·
維護者通常 1 天內回覆
-
bug trace-provider
難度 4/5 3-5 天 新手友好度 48/100
chainloop-dev/chainloop#3803 ·
維護者通常 1 天內回覆
-
feat(trace): support GitHub Copilot (CLI and VS Code) in Chainloop Trace可能已有人在做 @migmartri 今天認領。 未關閉Feature spec trace-provider
chainloop-dev/chainloop#3800 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Allow enabling policy enforcement at the workflow contract level可能已有人在做 @migmartri 於 10 天前認領。 未關閉component/backend new-policy spec
chainloop-dev/chainloop#3762 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
chainloop component/CLI performance trace-provider
難度 4/5 3-5 天 新手友好度 62/100
chainloop-dev/chainloop#3756 ·
維護者通常 1 天內回覆
查看 chainloop-dev/chainloop 的全部 Issue
相似的 Issue
-
GitHub webhook is not subscribed to release events, so `event: release` never triggers可能已有人在做 @qsun 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
woodpecker-ci/woodpecker#7542 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
維護者通常 1 天內回覆
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未關閉
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
model:sonnet runtime:claude security size:S
難度 2/5 1-3 小時 新手友好度 78/100
FootprintAI/Containarium#3624 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆