Repository navigation
Verify single-record streaming against the locked server - #11
Merged
Merged
Conversation
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
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.
Exercise the single-record Execute protocol with SDK v0.7.0 and protocol v0.5.0, including rejection before effects and rejection after an acknowledged mutation. Preserve direct owner routing, bounded cumulative reads and independent single-record callers for the database saturation comparison.
Remove redundant client ownership fields and inaccurate overwritten provenance values. Lock the merged server source, module version and checksum so integration and comparison runs use a reproducible binary. Validation includes offline race/vet/tagged compilation, dependency and lock checks, independent review, and real MongoDB/Search integration with fixture cleanup receipts.