mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-10 10:06:12 +00:00
pingqiuandClaude Opus 4.6
1c7154a11a
Add detailed coverage mapping of 43 existing tests against the test roster. Identify 7 missing component tests and 3 missing integration tests with concrete scenarios, file placement, and must-prove criteria. Key finding: every tester-found bug during T1-T5 was a wiring bug caught by reviewing the production path, not by unit tests on pure logic. This confirms component tests are the highest-value gap for CI/CD protection. Priority order: Tier 1 (7 component tests, do now), Tier 2 (3 integration tests, do before hardware), Tier 3 (4 hardware scenarios, T6/T7). 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