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

Ouverte
  • Quelque chose ne va pas ?
#645 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
38/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
aws, go
Domaine
devtools, security, testing-qa

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Go
Étoiles
0
Forks
0
Merge moyen
6 h 16 min
PR mergées (30 j)
243

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de coder/openstorage

Toutes les issues de coder/openstorage

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.