verification skills: remaining follow-ups (RepoPurger model, S3 multipart ModTime, osv.sh cleanup edge cases)

未關閉
#645 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
aws, go

研究方向

Start with .agents/skills/verify-orphan-sweep/ and .agents/skills/verify-openstorage/scripts/osv.sh, then read the referenced follow-ups in #641 and #643. The work spans a TLA+ model, cleanup symlink and redaction handling, and an AWS S3 multipart check that is blocked on an approved account, bucket, and spend cap. Done means those cases are covered and cleanup does not leave readable raw tokens after a redaction error.

由索引模型根據 Issue 內容生成。

描述

testing tracking

These verification-skill follow-ups remain after #628 closed. #641 fixed #628 items 1 and 2, and #643 fixed item 4.

verify-orphan-sweep (.agents/skills/verify-orphan-sweep/)

  1. The model does not cover RepoPurger. It needs a TLA+ model of its own: purge eligibility, the delete guard, and the race with a write that re-registers a pack.
  2. S3 multipart ModTime is untested. On AWS S3, a multipart-created object gets the upload's start time as its date, so a quarantine copy of a pack over 5 GiB ages from the start of the copy. This needs a real AWS bucket, which waits for an approved account, bucket and spend cap.

verify-openstorage (.agents/skills/verify-openstorage/scripts/osv.sh)

  1. cleanup copies serve logs and state.env into fixed evidence names with cp, and writes tokens.txt with a redirect. Both write through a symlink planted at those paths, as before #641. Only the run owner can plant one, because the run directory is private. Fix idea: refuse a symlink at each fixed target.
  2. When the redaction walk hits an unreadable entry, it stops part-way, so later files keep raw tokens until a rerun. Cleanup does exit 1 and keeps work/, so a rerun after fixing the mode redacts them. Fix idea: redact every readable file first, then fail.

Owner: @ThomasK33. Trigger: the next change to either skill, or before agents rely on the skill evidence for a release.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: xhigh

主要語言
Go
星號
0
分支
0
平均合併
6 小時 16 分鐘
30 天內合併 PR
243

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

coder/openstorage 的其他 Issue

查看 coder/openstorage 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。