Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

TieredEventStore reports existing streams as missing

Aperta
  • Qualcosa non va?
#612 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 7 giorni

@nmummau ci sta già lavorando.

Dal 14/10/2026.

  • #623 di @nmummau — aperta

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
1/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend

Direzione di ricerca

The issue names TieredEventStoreTests.cs in src/Core/test/Eventuous.Tests.Application and the TieredEventStore implementation. Start by reviewing the committed change on fix/issue-609-tiered-store and its 15 tiered-store tests; the issue reports that all 36 application tests pass. The fix is already committed locally, so this work is underway and is not a suitable first contribution.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Related test issue

Discovered while implementing #609 — tiered event-store coverage.

Problem

TieredEventStore.StreamExists effectively requires a stream to exist in both the hot and archive stores. Streams that exist in only one tier are incorrectly reported as missing. Existence checks also fail to account for an archive exposed only through IEventReader, which the constructor accepts.

This makes the existence result inconsistent with readable data: an archived stream can still be read after hot-store deletion, yet StreamExists returns false.

Reproduction

  1. Create separate hot and archive InMemoryEventStore instances.
  2. Append events to a stream in only the hot store.
  3. Construct TieredEventStore(hot, archive) and call StreamExists for that stream.
  4. Repeat with events in only the archive store.

Actual: both single-tier cases return false.

Expected: a stream exists if either tier contains it.

Hot tier Archive tier Expected result
Missing Missing false
Present Missing true
Missing Present true
Present Present true

Fix and acceptance criteria

  • Return true when the hot store contains the stream, without requiring an archive lookup.
  • Otherwise check archive existence directly when it implements IEventStore.
  • For an archive implementing only IEventReader, establish existence with a bounded read according to that interface's missing-stream contract.
  • A successful empty read represents an existing empty stream; StreamNotFound represents absence.
  • Archive failures and cancellation propagate rather than being converted into false.
  • Dispose the archive enumerator and forward cancellation to the read.
  • Deleting the hot copy does not make an existing archive copy disappear from the existence result.
  • Preserve existing cross-tier read behavior and hot-only append, truncate, and delete behavior.

Existing regression tests and implementation

TieredEventStoreTests.cs in src/Core/test/Eventuous.Tests.Application reproduced five failing cases before the fix:

  • Hot-only stream existence.
  • Archive-only stream existence.
  • An existing stream in an archive exposed only as IEventReader.
  • An empty existing stream in a read-only archive.
  • Existence after deleting the hot copy while retaining the archive copy.

Additional tests cover archive failures, cancellation, an unavailable archive when the hot stream exists, bounded reads across tiers, and hot-only mutations.

An implementation is already committed locally on fix/issue-609-tiered-store, commit 1639f36c. All 36 tests in the application test project pass on .NET 10, including 15 tiered-store cases. The branch has not been published or merged as part of this work.

Lingua principale
C#
Stelle
512
Fork
99
Merge medio
5g 6h
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Eventuous/eventuous

Tutte le issue di Eventuous/eventuous

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.