Adopt JasperFx 2.39.1 and compliance wave 4 - #410
Merged
Conversation
Bumps JasperFx, JasperFx.Events, JasperFx.Events.ComplianceTests and both source generators 2.38.0 -> 2.39.1, and enrolls the four new shared suites that shipped in it (JasperFx/jasperfx#620): - fetch_for_writing_compliance (13) - stream_read_compliance (11) - event_metadata_compliance (9) - live_aggregation_compliance (7) Polecat's compliance coverage goes from 65 to 105 tests with zero capability gates. PolecatComplianceFixture resolves the new ComplianceStoreConfig.EnableHeaders flag onto Events.EnableHeaders, alongside the existing correlation wiring. The flag exists because the two products spell it differently -- stamping the headers themselves needed nothing new, since IEvent.SetHeader is already shared. Verified on net9.0: 105/105 compliance and 1703/0/3 for the full Polecat.Tests suite against the published 2.39.1 packages. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde
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 JasperFx 2.38.0 → 2.39.1 and enrolls the four compliance suites that shipped in it (JasperFx/jasperfx#620).
fetch_for_writing_compliancestream_read_complianceevent_metadata_compliancelive_aggregation_compliancePolecat's compliance coverage goes 65 → 105 tests, zero capability gates.
Verified
Against the published 2.39.1 packages, net9.0:
The suites were authored against a Polecat working copy from the start (via the
ComplianceSourceDirdev loop this repo already supports), so they were passing here before the upstream PR was opened — not ported blind and fixed afterwards.The one code change
PolecatComplianceFixtureresolves the newComplianceStoreConfig.EnableHeadersflag ontoEvents.EnableHeaders, alongside the existing correlation wiring. That flag exists only because the two products spell it differently (Marten usesEvents.MetadataConfig.HeadersEnabled); stamping the headers themselves needed nothing new, becauseIEvent.SetHeaderis already on the shared event interface.Nothing else in Polecat changed. Everything the four suites exercise —
FetchForWriting,WriteToAggregate,AppendOptimistic/AppendExclusive,FetchStreamAsyncwith its version/timestamp bounds,FetchStreamStateAsync, theIEventenvelope,AggregateStreamAsync/AggregateStreamToLastKnownAsync— was already reachable through the shared JasperFx surfaces.Note on live aggregation
LiveAggregationCompliancedeliberately folds an unregistered aggregate type rather than callingconfig.LiveAggregation<T>(), because Polecat derives live aggregators automatically and setsSupportsLiveAggregationRegistration => false. Folding an unregistered type is the common ground between the two stores, so the suite needs no capability gate here.Marten's matching adoption is JasperFx/marten#5176.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde