• Joined on 2026-04-07
dailz opened issue dailz/go-kv#10 2026-06-09 13:08:25 +08:00
[Important] MemTable 写入失败(Arena 满)在 WAL 写入后未覆盖
dailz opened issue dailz/go-kv#9 2026-06-09 13:08:05 +08:00
[Critical] Go 内存模型:lock-free read 需要原子发布机制
dailz opened issue dailz/go-kv#8 2026-06-09 13:07:51 +08:00
[Critical] 恢复后未确认 Batch 可能变成已发布
dailz opened issue dailz/go-kv#7 2026-06-09 13:07:40 +08:00
[Critical] 预创建 segment 可破坏尾部截断逻辑
dailz opened issue dailz/go-kv#6 2026-06-09 13:07:29 +08:00
[Critical] Segment 边界跨 Batch 行为未定义
dailz opened issue dailz/go-kv#5 2026-06-09 13:07:11 +08:00
[Critical] WAL write failure 语义过于简化:write() 失败后 bytes 可能已落盘
dailz pushed to main at dailz/go-kv 2026-06-09 11:58:21 +08:00
0047d52541 update design doc
dailz closed issue dailz/go-kv#3 2026-06-09 11:39:14 +08:00
3.2 WAL:评估 Value Log 先 fsync 再 WAL fsync 对写吞吐的影响
dailz closed issue dailz/go-kv#4 2026-06-09 11:39:14 +08:00
3.2 WAL:补充 ErrCommitUnknown 的 API 层提交状态确认约束
dailz closed issue dailz/go-kv#1 2026-06-09 11:39:14 +08:00
3.2 WAL:澄清 WAL write failure 与 MemTable pending entry 的时序
dailz closed issue dailz/go-kv#2 2026-06-09 11:39:14 +08:00
3.2 WAL:明确 write-stopped 后 pending/aborted entry 生命周期
dailz closed issue dailz/logViewer#14 2026-06-09 11:27:45 +08:00
🟡 [M4] watcher 后端错误被静默丢弃
dailz commented on issue dailz/logViewer#14 2026-06-09 11:27:39 +08:00
🟡 [M4] watcher 后端错误被静默丢弃

修复提交: 7852e92

修复内容:

  • FileEvent enum 新增 WatcherError { message: String } 变体,用于传递 notify 后端错误
  • 回调中 Err(_) => return 替换为 try_send(FileEvent::WatcherError)
dailz commented on issue dailz/logViewer#13 2026-06-09 10:49:01 +08:00
🟡 [M3] read_cache 零长度读取命中空缓存槽

修复方案

根因

缓存命中条件 slot.block_offset == aligned_key && request_end <= slot.block_offset + slot.len 未检查 slot.len > 0,导致初始化状态的空槽(block_offset=0, len=0)被…

dailz closed issue dailz/logViewer#13 2026-06-09 10:48:43 +08:00
🟡 [M3] read_cache 零长度读取命中空缓存槽
dailz pushed to master at dailz/logViewer 2026-06-09 10:48:43 +08:00
d37ed6df68 fix(io): harden read_cache against zero-length false hits and overflow (closes #13)
dailz opened issue dailz/go-kv#4 2026-06-09 10:31:52 +08:00
3.2 WAL:补充 ErrCommitUnknown 的 API 层提交状态确认约束
dailz opened issue dailz/go-kv#3 2026-06-09 10:31:52 +08:00
3.2 WAL:评估 Value Log 先 fsync 再 WAL fsync 对写吞吐的影响
dailz opened issue dailz/go-kv#2 2026-06-09 10:31:52 +08:00
3.2 WAL:明确 write-stopped 后 pending/aborted entry 生命周期
dailz opened issue dailz/go-kv#1 2026-06-09 10:31:52 +08:00
3.2 WAL:澄清 WAL write failure 与 MemTable pending entry 的时序