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

Aberta
  • Algo errado?
#645 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
38/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
aws, go
Domínio
devtools, security, testing-qa

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Go
Estrelas
0
Forks
0
Merge médio
6h 16min
PRs com merge (30d)
243

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de coder/openstorage

Todas as issues de coder/openstorage

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.