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

2026-06-09 - 2026-06-12
Period: 3 days
1 day 3 days 1 week 1 month 3 months 6 months 1 year

Overview

0 Active Pull Requests
14 Active Issues
0
Merged Pull Requests 0
Proposed Pull Requests 14
Closed Issues 14
New Issues
Excluding merges, 1 author has pushed 5 commits to main and 5 commits to all branches. On main, 1 file has changed and there have been 234 additions and 45 deletions.

14 Issues closed from 1 user

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 #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

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

14 Issues created by 0 users

Opened #1 3.2 WAL：澄清 WAL write failure 与 MemTable pending 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 #2 3.2 WAL：明确 write-stopped 后 pending/aborted 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