dailz/go-kv
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Pulse Contributors Code Frequency Recent Commits

2025-08-24 - 2026-08-24
Period: 1 year
1 day 3 days 1 week 1 month 3 months 6 months 1 year

Overview

0 Active Pull Requests
21 Active Issues
0
Merged Pull Requests 0
Proposed Pull Requests 21
Closed Issues 21
New Issues
Excluding merges, 1 author has pushed 36 commits to main and 36 commits to all branches. On main, 102 files have changed and there have been 18161 additions and 332 deletions.

21 Issues closed from 1 user

Closed #20 设计审查: Periodic/Never 落盘策略下 fsync 错误的上报机制 2026-06-12 09:35:51 +08:00

Closed #19 设计审查: WAL 内部缓冲模型 — 私有 encode buffer vs 共享 buffered writer 2026-06-12 09:35:51 +08:00

Closed #21 设计审查: Get API 必须返回 found 状态以支持空值确认约束 2026-06-12 09:35:51 +08:00

Closed #18 设计审查: publishedSequence 的范围 — 物理 mutation 还是包含 MVCC commit record 2026-06-12 09:24:22 +08:00

Closed #17 设计审查: MANIFEST 职责边界 — checkpoint vs WAL 恢复终点 2026-06-12 09:15:41 +08:00

Closed #16 设计审查: Segment ID 连续性要求与旧 segment 删除后的 gap 处理 2026-06-12 08:52:47 +08:00

Closed #15 设计审查: WAL segment 大小未定义，最大 batch 可能无法写入空 segment 2026-06-12 08:39:26 +08:00

Closed #14 [Important] publishedSequence 需要明确的内存序约束 2026-06-11 20:36:15 +08:00

Closed #13 [Important] Batch 校验缺少资源上限 2026-06-11 20:27:18 +08:00

Closed #12 [Important] 尾部截断后缺少持久化步骤 2026-06-11 20:17:59 +08:00

Closed #11 [Important] CURRENT 文件权威性与实际恢复模型不一致 2026-06-11 20:09:55 +08:00

Closed #10 [Important] MemTable 写入失败（Arena 满）在 WAL 写入后未覆盖 2026-06-11 19:53:25 +08:00

Closed #9 [Critical] Go 内存模型：lock-free read 需要原子发布机制 2026-06-11 18:30:07 +08:00

Closed #8 [Critical] 恢复后未确认 Batch 可能变成已发布 2026-06-11 18:15:21 +08:00

Closed #7 [Critical] 预创建 segment 可破坏尾部截断逻辑 2026-06-11 17:52:35 +08:00

Closed #6 [Critical] Segment 边界跨 Batch 行为未定义 2026-06-11 17:33:52 +08:00

Closed #5 [Critical] WAL write failure 语义过于简化：write() 失败后 bytes 可能已落盘 2026-06-09 13:38:17 +08:00

Closed #4 3.2 WAL：补充 ErrCommitUnknown 的 API 层提交状态确认约束 2026-06-09 11:39:14 +08:00

Closed #2 3.2 WAL：明确 write-stopped 后 pending/aborted entry 生命周期 2026-06-09 11:39:14 +08:00

Closed #1 3.2 WAL：澄清 WAL write failure 与 MemTable pending entry 的时序 2026-06-09 11:39:14 +08:00

Closed #3 3.2 WAL：评估 Value Log 先 fsync 再 WAL fsync 对写吞吐的影响 2026-06-09 11:39:14 +08:00

21 Issues created by 0 users

Opened #2 3.2 WAL：明确 write-stopped 后 pending/aborted entry 生命周期 2026-06-09 10:31:52 +08:00

Opened #4 3.2 WAL：补充 ErrCommitUnknown 的 API 层提交状态确认约束 2026-06-09 10:31:52 +08:00

Opened #1 3.2 WAL：澄清 WAL write failure 与 MemTable pending entry 的时序 2026-06-09 10:31:52 +08:00

Opened #3 3.2 WAL：评估 Value Log 先 fsync 再 WAL fsync 对写吞吐的影响 2026-06-09 10:31:52 +08:00

Opened #5 [Critical] WAL write failure 语义过于简化：write() 失败后 bytes 可能已落盘 2026-06-09 13:07:11 +08:00

Opened #6 [Critical] Segment 边界跨 Batch 行为未定义 2026-06-09 13:07:29 +08:00

Opened #7 [Critical] 预创建 segment 可破坏尾部截断逻辑 2026-06-09 13:07:40 +08:00

Opened #8 [Critical] 恢复后未确认 Batch 可能变成已发布 2026-06-09 13:07:51 +08:00

Opened #9 [Critical] Go 内存模型：lock-free read 需要原子发布机制 2026-06-09 13:08:05 +08:00

Opened #10 [Important] MemTable 写入失败（Arena 满）在 WAL 写入后未覆盖 2026-06-09 13:08:25 +08:00

Opened #11 [Important] CURRENT 文件权威性与实际恢复模型不一致 2026-06-09 13:08:38 +08:00

Opened #12 [Important] 尾部截断后缺少持久化步骤 2026-06-09 13:08:50 +08:00

Opened #13 [Important] Batch 校验缺少资源上限 2026-06-09 13:09:01 +08:00

Opened #14 [Important] publishedSequence 需要明确的内存序约束 2026-06-09 13:09:15 +08:00

Opened #15 设计审查: WAL segment 大小未定义，最大 batch 可能无法写入空 segment 2026-06-12 08:28:03 +08:00

Opened #16 设计审查: Segment ID 连续性要求与旧 segment 删除后的 gap 处理 2026-06-12 08:28:10 +08:00

Opened #17 设计审查: MANIFEST 职责边界 — checkpoint vs WAL 恢复终点 2026-06-12 08:28:17 +08:00

Opened #18 设计审查: publishedSequence 的范围 — 物理 mutation 还是包含 MVCC commit record 2026-06-12 08:28:24 +08:00

Opened #19 设计审查: WAL 内部缓冲模型 — 私有 encode buffer vs 共享 buffered writer 2026-06-12 08:28:34 +08:00

Opened #20 设计审查: Periodic/Never 落盘策略下 fsync 错误的上报机制 2026-06-12 08:28:42 +08:00

Opened #21 设计审查: Get API 必须返回 found 状态以支持空值确认约束 2026-06-12 08:28:49 +08:00