Upgrade JasperFx family → 2.12.0 + dead-letter row drill-in / per-tenant counts#4740
Merged
Merged
Conversation
Implement the per-tenant IEventDatabase.FetchDeadLetterCountsAsync(tenantId) overload: filter the store-global dead-letter table by the DeadLetterEvent.TenantId now recorded per row, so partitioned stores attribute projection dead letters to the owning tenant. Null tenant falls back to the store-global (tenant-collapsed) shape. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…CritterWatch#369) The companion to CountDeadLetterEventsAsync: fetch the actual dead-letter event rows for a shard (id, sequence, exception, timestamp, tenant), most-recent-first by EventSequence, paged via offset/limit, optionally scoped to one tenant partition. Default interface method returns empty so stores without dead-letter persistence are unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pulls in #453: IEventDatabase.QueryDeadLetterEventsAsync, DeadLetterEvent.TenantId, and the tenant-aware daemon surface. Marten implements the new dead-letter row query + per-tenant FetchDeadLetterCountsAsync (cherry-picked above). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 15, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the JasperFx family
2.10.0 → 2.12.0and implements the twoIEventDatabasedead-letter surfaces that 2.12.0 (#453) adds.Changes
Directory.Packages.props— JasperFx / JasperFx.Events / JasperFx.Events.SourceGenerator / JasperFx.SourceGenerator →2.12.0.QueryDeadLetterEventsAsync(Support for automatically append events from aggregates #369) —MartenDatabaseimplements the newIEventDatabase.QueryDeadLetterEventsAsync: fetch the actual dead-letter event rows for a shard (id, sequence, exception type/message, timestamp, tenant), most-recent-first, paged, optionally scoped to one tenant. Companion to the existingCountDeadLetterEventsAsync.FetchDeadLetterCountsAsync(Introduce a global sequence number in the event store #381) — tenant-scoped override of the dead-letter count fetch, readingDeadLetterEvent.TenantId(new in 2.12.0).Verification
dotnet build src/Marten/Marten.csprojis green against the published JasperFx.Events 2.12.0 — the implementations override 2.12.0's new interface method and read the newDeadLetterEvent.TenantId, so a green compile confirms the published surface matches.🤖 Generated with Claude Code