Design

Source merged; no new production release: PR #239 merged into main on 2026-10-17 as fbcb51197, closing #218 and retaining the original author commits. Merging source does not update installed software. This is the current design decision for #218 …

Decision, 2026-10-16: GO; source acceptance and merge complete. Server PR #242 merged the signed repair commit 2616d43fb into main as 4e55fc7db. The final candidate was verified directly on main’s 00a375c4e baseline, independently of the pending LIST …

Release follow-up (2026-10-15): This repair first shipped in Server 20261015. The source acceptance below records the earlier pre-release verification. Verified on 2026-10-15: merged on main, not yet in a published Server release. PR #233 was merged …

Status, 2026-09-17. The Go TLS default repair 48e184652 shipped in Server 20260916. The reporter of issue #154 retested on that release and reports the same connection reset by peer on OIDC discovery. No root cause is established for that …

Warning 历史 LIST 设计已由新决策覆盖 · Earlier LIST design superseded (2026-10-17) English: The investigation below is retained as historical evidence. Its current-design and pending-work guidance is superseded by the latest LIST recovery decision (English). …

Publication update, 2026-09-17: The Go TLS default repair (48e184652) shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The later repairs in #129, #134 and #178 shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The federated CopyObject repairs recorded here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Publication update, 2026-09-17: The #77 repair recorded here shipped in Server 20260916; deletion-record export stays off by default. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and …

Publication update, 2026-09-17: The repairs recorded here (PR #162, the second-round PR #196 and the third-round purge repairs) shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Warning 旧版分片列举设计已被覆盖 · Earlier multipart-listing designs superseded (2026-10-17) English: The #79 multipart-listing proposals, enablement advice and status in this article are historical. Subsequent design work is governed by the latest design …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …

Warning 旧版分片列举设计已被覆盖 · Earlier multipart-listing designs superseded (2026-10-17) English: The August analysis and September legacy/strict proposal retained below are superseded by the latest design decision (English). It selects one persistent …

This is the design and implementation record for MCLI’s read-only checksum verification workflow and pgsty/mc#5, the non-TTY output defect found during release review. Status: shipped in the final mcli 20260903 release. The command merged to main …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …

Publication update, 2026-09-17: The streaming-checksum follow-up (PR #143) shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …

Publication update, 2026-09-17: The September source repairs discussed here shipped in Server 20260916. Coordinated upgrades, opt-in prerequisites and remaining limitations still apply. Dated source-status and validation records below retain their …

PR #57, contributed by Shooks (@Dansyuqri), fixed #47. The repair is included in Server 20260903. This records the response contract; production deployment remains specific to the artifact and installation an operator actually runs. The defect and …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …

Historical scope: this is the Console 2.2.0 progress repair, included in Server 20260903’s embedded Console. Console 2.4.1 subsequently added file streaming and native browser handoff, eliminating the complete JavaScript ZIP Blob. Transport …

Status: shipped in SILO Console 2.2.0 · Owner: pgsty/silo-console · Tracking: pgsty/silo#17 · Review: consensus of product, security, and frontend architecture reviews SILO Console can preview images, PDFs, audio, and video, but not the small logs, …

Release check (2026-09-16): the original repair described here is included in Server 20260903. Dated review and test accounts below record their original evidence, not a still-pending release or acceptance of a particular production installation. …