fix: detect noisy Windows ARM64 SSH platforms#7965
Conversation
- Scan remote platform probe output line-by-line for supported OS/arch markers. - Handle PowerShell/OpenSSH first-use CLIXML or banner noise before Windows ARM64. - Add regression coverage for noisy Windows ARM64 detection.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis change refactors platform detection parsing in the SSH remote platform detection module. A new shared helper, parseRemotePlatformOutput, replaces the previous ad-hoc field extraction used separately by detectUnamePlatform and detectWindowsPlatform. The helper iterates output line-by-line, extracts fields per line, and attempts to derive a RelayPlatform, returning the first successful match. A new test case was added verifying correct Windows ARM64 detection when PowerShell output contains noise preceding the platform marker. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
Summary
#< CLIXML ... Windows ARM64, which previously caused Orca to parse the first noisy fields and returnnull, leading to the unsupported platform error.Screenshots
No visual change.
Testing
pnpm lintpnpm typecheckpnpm testpnpm buildAdditional focused test run:
AI Review Report
Reviewed the fix against #7706 from a maintainer perspective.
ssh:connectfails during remote relay platform detection before deployment.