transport: add turmoil support - #88
Open
jttdd wants to merge 1 commit into
Open
Conversation
Author
|
@kezhuw any thoughts on this? something you'd be willing to land? |
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.
this PR adds optional turmoil socket support to be able to run the client within a turmoil simulation.
I’d like to use this client in deterministic simulation tests, where I can exercise connection loss, partitions, delayed traffic, retries, and session behavior without relying on timing-sensitive real sockets or external ZooKeeper infrastructure. Turmoil is a good fit for that kind of coverage, and this change keeps the support small and opt-in while preserving the crate’s existing async-runtime-agnostic shape.