mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 15:04:37 +00:00
pingqiuandClaude Opus 4.6
4681df6b56
Findings fixed: 1. TestAdversarial_ReconnectUsesHandshakeNotBootstrap now has 3 observable proof points instead of just "SyncCache succeeded": - new shipper HasFlushedProgress=true (seeded from old group) - replica receivedLSN advances during SyncCache (catch-up delivered entries) - shipper replicaFlushedLSN > 0 after barrier (durable progress established) Bootstrap alone would not advance receivedLSN — it only sends the barrier. 2. TestBug2 stale comment removed: "must NOT call SetReplicaAddr" replaced with accurate CP13-5 explanation that SetReplicaAddrs now preserves hasFlushedProgress across shipper replacement. 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