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

Test partitioned subscription ordering, concurrency, and shutdown

オープン
#606 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

まだ誰も着手していません。

評価

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

調査の方向性

Start with src/Eventuous.Subscriptions/Filters/PartitioningFilter.cs and the existing subscription tests to find how to configure a consume pipeline and observe partition metadata. Add coordinated tests for ordering, independent progress, key assignment, and graceful shutdown, using bounded waits and no external broker. Done means all acceptance criteria pass; run the focused subscription tests and collect coverage for this path.

索引モデルが issue の本文から書いたものです。

説明

Problem

PartitioningFilter has no recorded line coverage in the October 5, 2026 .NET 10 coverage run. It selects a partition and routes each message through a serial handling worker, so failures here could reorder events, block unrelated work, or lose accepted messages during shutdown. You can view a test coverage report I generated here: index.html

Source: PartitioningFilter.cs.

Proposed tests

  • Send multiple events for the same stream through a configured consume pipeline. Block the first handler and verify that later events in its partition cannot overtake it.
  • Send events to distinct partitions and verify that an unblocked partition can progress while another handler is blocked.
  • Verify default stream-based partitioning and a configured custom partition key through the partition metadata received by handlers.
  • Exercise different keys that map to the same partition and verify serial processing within that partition.
  • Begin shutdown while accepted work is queued. Verify that graceful shutdown waits for that work to finish and does not process messages twice.

Acceptance criteria

  • Ordering and independent progress are asserted through actual message handling in a consume pipeline.
  • Default and custom partition keys produce the expected handler-visible partition metadata.
  • Graceful shutdown accounts for every accepted message before completing.
  • Tests use explicit coordination signals and bounded waits instead of arbitrary sleeps to establish ordering.
  • Tests do not call the hashing implementation or task extensions directly.
  • No external broker or Docker container is required.

Validation

Run the focused subscription tests and collect coverage for the partitioning path. Use controlled keys or an injected hash where needed to make partition assignment deterministic, while retaining a test of the default configuration.

主要言語
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 を短くまとめたダイジェスト。