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

Đang mở
  • Có gì không ổn?
#347 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
12/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
go, json
Lĩnh vực
cli, devops

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.

Ngôn ngữ chính
Go
Star
2
Fork
6
Merge trung bình
2 giờ 39 phút
Pull request đã merge (30 ngày)
74

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Judgment-Pack/judgment-pack-runtime

Tất cả issue của Judgment-Pack/judgment-pack-runtime

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.