Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Verify tiered event-store existence and write-routing behavior

オープン
  • 何か問題がありますか？
#609 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 7 日以内に返信

@nmummau がすでに取り組んでいます。

2026年10月14日 から。

  • #623 @nmummau による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
52/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
csharp
領域
backend, testing

調査の方向性

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 expose StreamExists.

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時間
マージ済み PR（30日）
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Eventuous/eventuous のほかの issue

Eventuous/eventuous の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。