Repository navigation
Explain the Active Server stop refusal in Settings - #26584
Conversation
4a2c87a to
87eb8a7
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (6)
🚧 Files skipped from review as they are similar to previous changes (6)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 5 remain after this review. 📝 WalkthroughWalkthroughThe managed-server outcome label now gives an instruction when a stop is refused because the server is active. Tests cover this refusal and running-terminal and unverifiable-census outcomes. English, Spanish, French, Japanese, Korean, and Chinese locale files add translations for the active-server message. Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The active-server refusal now gives users the intended instruction without changing the other refusal messages. No issue identified here needs resolution before merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
87eb8a7 to
af2c326
Compare
ELI5
Stopping the selected Active Server was safely refused, but Settings told users to close running terminals even when the host had none. It now tells them to choose another Active Server in Advanced first.
What Changed
The existing localized outcome formatter handles
orcad_stop_active_environmentbefore the general live-terminal verdict. All six supported language catalogs include the instruction. Running-terminal and unverifiable refusals retain their existing wording.Rebased onto main (Phase 3/3.5). The Docker SSH end-to-end spec and its CI-lane routing were dropped to keep this a product-only change; the unit tests cover the mechanism.
Why
The main process already provides a specific refusal code, but the UI grouped every
liveverdict under running terminals. Matching that code gives users the useful next step without changing stop policy, displaying raw backend text, or changing the verdict contract.Linked Issue
Found while validating #26483. Independent fix against
OrcaWin/phase35.Visual Proof
Before: selected host and “Running terminals: 0” remain visible while Stop tells the user to close terminals.
After: Stop explains how to change the Active Server; the host remains available.
Baseline failure: active-server-stop-copy-runtime-red.log
Corrected run: active-server-stop-copy-runtime-green.log
Testing
Hidden macOS Electron client + real Linux Docker SSH host using the exact installed
1.4.223-adhoc.20261008080519server template. Baseline fails; corrected UI flow passes in 13.1 seconds. No Windows runtime claim.77 tests across six files pass, including the existing main-process active-server guard, refusal wording, and CI routing. Full
pnpm tc,pnpm lint(including localization checks), changed-code quality, fresh Electron E2E build, and commit hooks pass.Review
Six product-code lines add the specific localized outcome. The host’s stop guard and process handling are unchanged.
Agent skill upstream boundary
Notes
No new transport calls, wire fields, timers, style changes, or platform-specific behavior. The fix uses an existing code and applies equally to repository and folder workspaces. Contact loss stays unverifiable.
Checklist