Repository navigation
Add SliM runtime controls and transports - #7
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.
The Rust SliM server previously continued executing after stop/ignore fixture results and left transport setup, timeout flags, request flushing, and stdio log handling to each consumer. This adds structured V0.5 control results with exact wire tags, stops the remainder of the current batch, and keeps the connection available for later batches.
It also adds whole-second
-stimeout options with the documentedTIMED_OUT nresult, supported TCP/port-1 runners, explicitSOUT/SERRoutput tunnels, and client request flushing. The proc macro preserves structured controls from methods and constructors. Temoc now drains port-1 stderr concurrently, preventing a full pipe from deadlocking the child and avoiding duplicate tunneled output.The timeout model is deliberately observational: an overrun is reported after in-process fixture code returns, so existing side effects remain and arbitrary Rust code is never forcibly cancelled. Transparent process-wide
println!capture also remains outside this safe API; stdio fixtures write throughOutputTunnel.Validation:
cargo test --workspace --all-featurescargo clippy --workspace --all-features -- -D warningscargo fmt --all -- --checkgit diff --checkAn independent review against the V0.5 protocol and current FitNesse execution behavior found no remaining blockers.