Fix proxy failover status output#144
Merged
unive3sal merged 1 commit intoSaladDay:mainfrom May 7, 2026
Merged
Conversation
Collaborator
|
Thanks for your contribution! Would you please rebase your commit for review? |
2fa4c18 to
b72ac76
Compare
Contributor
Author
|
Rebased, should be OK now. Please take another look. |
Owner
|
LGTM, cc @unive3sal |
SaladDay
approved these changes
May 6, 2026
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.
Summary
Fixes #143.
This updates the CLI proxy output so it no longer hard-codes automatic failover as disabled. The proxy runtime already reads per-app
auto_failover_enabledand routes through the configured failover queue when enabled, so the old message was misleading.Changes:
cc-switch proxy show.cc-switch proxy serveprint the configured automatic failover status instead of saying it is disabled.Tests
cargo fmt --allcargo test cli::commands::proxy::tests::proxy_overview_lines --libcargo test proxy::provider_router::tests --libNote:
cargo test --libon my local macOS environment still has two unrelated proxy runtime/session failures that reproduce when run individually. One fails because a local cc-switch process is already listening on127.0.0.1:15721; the other ismanaged_session_ready_info_accepts_persisted_session_without_status_probe.