mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-23 22:40:39 +02:00
pingqiuandClaude Opus 4.7
7dfb0172d1
Annotates pillar 2 (dual-line execution) and pillar 3 (receiver
convergence) rows with the landed commits + concrete test names so
the design narrative tracks the code:
Pillar 2 — assembled-stack fault-injection
7d051e2 — C3 fault-injection (recovery-package layer, spy sink):
TestC3FaultInjection_BaseError_WalExitsViaCtx
TestC3FaultInjection_OuterCancel_BothLanesWindDown
TestC3FaultInjection_WalError_RunTerminates_NarrowVariantA
9f62ebe — Pillar 2 fault-injection on the assembled stack
(BlockExecutor + RecoverySink + Sender + WalShipper):
TestPillar2A_BaseError_AssembledStack_FailReason
TestPillar2B_LiveWrites_HighPressure_BarrierIntegrity
TestPillar2C_WireAbortMidSession_AssembledStack_RestoresEmitContext
Pillar 3 — receiver convergence under same-LBA conflict
291e652 — slice-1: same-LBA arbitration on transport stack
3495a12 — slice-1 polish (AchievedLSN assertion, replica==primary
comparison, comment fixes, companion-SHA list)
TestPillar3Slice1_ReceiverConvergence_LiveOverwritesBacklog_SameLBAs
(transport-stack only; slice-2 lifts to engine path
via dual_lane_engine_test.go)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
sw-block
Private WAL V2 and standalone block-service workspace.
Purpose:
- keep WAL V2 design/prototype work isolated from WAL V1 production code in
weed/storage/blockvol - allow private design notes and experiments to evolve without polluting V1 delivery paths
- keep the future standalone
sw-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: code prototypes and experiments.private/: private notes, phase development, roadmap, and non-public working material
Repository direction:
- current state:
sw-block/is an isolated workspace insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths