mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-18 22:14:33 +00:00
pingqiuandClaude Opus 4.6
ec63c18438
Two fixes: 1. TestReconnect_GapBeyondRetainedWal_NeedsRebuild: rewritten to test the real reconnect handshake gap detection path (R < S in reconnectWithHandshake). Sequence: establish sync → disconnect → release retention hold via timeout → write + flush to advance WAL past replica position → reconnect → handshake detects R=0 < S=9 → NeedsRebuild. Log proves: "reconnect: gap too large R=0 H=8 S=9" 2. TestReplicaState_RebuildComplete_ReentersInSync: reclassified from primary proof to support evidence (does not start from live NeedsRebuild shipper state, but proves rebuild mechanics work end-to-end). Co-Authored-By: Claude Opus 4.6 (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