fix(steer): enforce fail-fast assertion for empty service iterators#866
Open
Alpy16 wants to merge 2 commits into
Open
fix(steer): enforce fail-fast assertion for empty service iterators#866Alpy16 wants to merge 2 commits into
Alpy16 wants to merge 2 commits into
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.
Closes #859
Description
Initializing Steer with an empty collection of services leaves the routing middleware in an unresolvable invariant state. While poll_ready will trivially return Poll::Ready(Ok(())), any subsequent invocation of call will immediately panic because there are no underlying target services to route the request to.
This patch adds an explicit assert!(!services.is_empty(), ...) check to the Steer::new constructor, shifting an operational runtime risk into a fast, upfront failure.
Type of Change
Bug fix (non-breaking change enforcing defensive API boundaries)
Verification
Added a #[should_panic] integration test in tower/tests/steer/main.rs with explicit type hinting to satisfy the compiler's inference engine.
Verified workspace tests pass via cargo test --test steer --all-features.