Define a host storage-admission contract for write-capable Runtime commands

Aperta
  • Qualcosa non va?
#347 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, json
Ambito
cli, devops

Direzione di ricerca

The pinned evidence points to internal/audit/audit.go (append records, line limits, cooperative append lock) and internal/mcp/server.go (per-message bounds) as the starting places. The issue asks for an inventory of write-capable CLI and MCP paths plus a versioned storage-admission contract, which is design work rather than a single fix. Done would mean a documented contract and tests for concurrent writers, ENOSPC during staged writes, and recovery, and that is not a first-timer task.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Consumer: Desk #685, the v0.14.0 aggregate local-storage acceptance requirement.

This is a host-integration contract request based on pinned source inspection, not a disk-exhaustion reproduction or a claim of observed data loss. Per-object limits, process deadlines and bounded protocol output do not by themselves establish an aggregate filesystem budget.

Please identify an existing supported contract, or specify a versioned component contract, through which a host can reserve a finite write envelope before growth or external effects. It must cover startup/recovery, temporary and coexisting files, persistent results, concurrent/background writers and descendants. A component may instead document and prove an exact no-growth or finite-growth command contract where appropriate.

The host needs:

  • Exact original store/root identities and the complete permitted write destinations, preserving existing authority and descriptor contracts.
  • Bounds for logical bytes, allocation allowance and namespace growth, including settlement/recovery headroom. A persistent process needs per-operation admission or a proven finite lifetime allowance.
  • Refusal before admitted capacity is exceeded, with typed quota/storage uncertainty; no replay of completed effects after a persistence failure.
  • A crash/restart and cancellation contract retaining reservations until the admitted writers can no longer grow.
  • Focused concurrent-writer, staged-write/ENOSPC and recovery tests, plus a discoverable contract/version.

An externally enforced filesystem/confinement backend is another possible route; this issue does not assume such a backend already exists or change supported deployment requirements. Desk owns host admission and integration. Component owners decide the implementation and release milestone. No pin, code, milestone or release change is requested by filing this question.

Pinned evidence: Runtime v0.39.0 at 12793d2dd24d18549567ac422711a2b3c1489f04.

  • Audit writer contract appends project-owned evaluation records; its line limits and cooperative append lock do not state a host-wide storage reservation.
  • MCP server bounds individual messages. That is distinct from filesystem growth.

Please inventory the write-capable CLI/MCP paths, including selected audit/lock/signing destinations and temporary/recovery writes, and distinguish genuinely read-only commands. Preserve the original selected project and audit semantics; making required writes read-only is not acceptance. These inspected files do not constitute an exhaustive writer audit, and this report does not assert that every MCP command writes.

Lingua principale
Go
Stelle
2
Fork
6
Merge medio
2h 22m
PR unite (30g)
89

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Judgment-Pack/judgment-pack-runtime

Tutte le issue di Judgment-Pack/judgment-pack-runtime

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.