Verify tiered event-store existence and write-routing behavior
维护者通常 7 天内回复
评估
调研方向
Start with src/Core/src/Eventuous.Persistence/EventStore/TieredEventStore.cs and the affected persistence/application test project; review the TieredEventStore implementation and its public APIs. Build isolated in-memory or controlled stores, then test existence across tier combinations, forward and backward reads, appends, truncation, deletion, and an archive that only implements IEventReader. Completion means assertions document the existence contract and verify stored events and routing, with a regression test for any confirmed bug.
由索引模型根据 Issue 内容生成。
描述
Problem
TieredEventStore has no recorded line coverage in the October 5, 2026 .NET 10 coverage run. Its public behavior needs tests independent of the existing TieredEventReader tests. You can view a test coverage report I generated here: index.html
There is also a potential correctness bug: StreamExists returns hotExists && archiveExists. A stream present in only one tier is therefore reported as missing, even though the tiered reader can read from that tier. This is a code-review finding; add a reproducing test and confirm the intended contract before changing the implementation.
Source: TieredEventStore.cs.
Proposed tests
- Exercise stream existence when the stream is present in hot storage only, archive storage only, both stores, or neither store.
- Read through the tiered store's public forward and backward APIs, including a stream spanning both tiers. Assert event order, requested counts, and absence of duplicates.
- Append through both the single-stream and batch APIs. Verify that events reach hot storage and do not alter the archive.
- Truncate and delete through the tiered store. Verify that these operations affect only hot storage.
- Establish the existence-check contract when the archive implements only
IEventReader, which does not exposeStreamExists.
Acceptance criteria
- Tests reproduce the current behavior for streams present in only one tier.
- The intended existence contract is documented in the tests; any confirmed bug is fixed with a regression test.
- Reads, appends, truncation, and deletion are tested through the public tiered-store API with assertions on stored events.
- Archive-only readers are handled according to an explicit contract.
- Tests use isolated in-memory stores or controlled store implementations and do not require Docker.
Validation
Run the affected persistence/application test project and collect focused coverage for TieredEventStore. Use behavioral assertions as the completion criterion, not a percentage target. A full provider-suite rerun is not required for this isolated work.
- 主要语言
- C#
- 星标
- 512
- 派生
- 99
- 平均合并
- 5 天 6 小时
- 30 天内合并 PR
- 5
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Eventuous/eventuous 的其他 Issue
-
MongoDB integration tests fail on newer GitHub Actions runner kernels可能已有人在做 @nmummau 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
Eventuous/eventuous#626 · 2 条评论 ·
维护者通常 7 天内回复
-
`dotnet format style --verify-no-changes` fails with naming violations and unnecessary imports可能已有人在做 @nmummau 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 80/100
Eventuous/eventuous#624 · 1 条评论 ·
维护者通常 7 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
Eventuous/eventuous#627 · 1 条评论 ·
维护者通常 7 天内回复
-
SQL Server: `append_events` does not need the `@inserted` table variable可能已有人在做 @nmummau 于 6 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 20/100
Eventuous/eventuous#619 · 1 条评论 ·
维护者通常 7 天内回复
-
SQL Server: stream reads do one key lookup per event, and `IDX_EventsStream` duplicates `UQ_StreamIdAndStreamPosition`可能已有人在做 @nmummau 于 6 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 18/100
Eventuous/eventuous#618 · 1 条评论 ·
维护者通常 7 天内回复
查看 Eventuous/eventuous 的全部 Issue
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 65/100
KnifeLemon/Filee#294 ·
维护者通常 1 天内回复
-
mtg-decide submission
难度 2/5 1-3 小时 新手友好度 66/100
Fialuxe/MouthOfGod_System#288 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
gavin-wolfe/wolfden#104 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
[BUG] Still libmicrohttpd dependency is not removed properly from External-Dependency-Info.txt file可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭type/bug
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复