Add StreamData local command model properties - #8
Open
jeregrine wants to merge 1 commit into
Open
Conversation
This was referenced Sep 9, 2026
jeregrine
added this pull request to stack #14
September 9, 2026 20:19
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.
Problem
Hand-written scenarios cover individual Group behaviors, but interactions between metadata updates, owner death, subscriptions, and named-cluster cleanup can leave gaps. Dual-index consistency alone cannot detect two indexes that agree on incorrect contents.
Fix
Add StreamData command histories checked against an independent map/set model. After every command, compare public API results, complete local entries, exact and prefix queries, counts, monitor events, and ETS dual-index consistency across the default and named clusters.
Each example and shrink attempt gets fresh supervisors, symbolic owners backed by real processes, and a dedicated observer. Owner-death cleanup is explicitly settled before checking state and events. Reusing bounded process names avoids atom growth during shrinking.
Supporting information
The generator varies shard counts and favors a small set of shared keys, owners, and metadata values to exercise collisions and repeated operations. StreamData is a test-only dependency; production behavior is unchanged.
This is the local correctness foundation. Remote batch boundaries, equal-timestamp conflicts, stale replication, TTL, and fairness need separate targeted properties. Reproducing a generated history does not reproduce BEAM scheduling.