fix(cli): warn on incomplete inference route - #9473
Conversation
Signed-off-by: Rebecca Sliter <571084+rsliter@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan includes up to 12 reviews per rolling hour; 10 remain after this review. 📝 WalkthroughWalkthroughThe inference route check now reports ChangesInference route status
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change correctly requires both the provider and model before reporting a healthy inference route, while preserving warnings for incomplete routes; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall coverage in commit fc7faff in the TypeScript / code-coverage/cliThe overall coverage in commit fc7faff in the Show a code coverage summary of the most impacted files.
Updated |
PR Review Advisor — No blocking findings reportedAdvisor assessment: No blocking advisor findings reported Model lanes
Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests. E2E guidanceAdvisory only. A maintainer can dispatch the default E2E suite for the commit under review. Recommended E2E: Manual-only E2E: This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge. |
rsliter
left a comment
There was a problem hiding this comment.
Security review: PASS at fc7faffb8eeb66c05aadab2d51df0eddab1eb487 against base 9ab3cd3a569e6d01aef26dee876461d281aef06a.
I reviewed authentication and authorization, command construction, credential and log handling, filesystem and network behavior, dependencies, privileges, concurrency, and failure behavior.
The production change only tightens a pure diagnostic classification from either route field being known to both fields being known. It does not add a probe, mutate route state, read credentials, change policy, touch the filesystem, or perform an external write. The four boundary states have exact status, detail, and recovery-hint coverage.
All substantive repository gates pass at the reviewed commit. The remaining failed Nemotron advisor job reports that its analysis did not complete and contains no code finding.
prekshivyas
left a comment
There was a problem hiding this comment.
Reviewed at fc7faff. No actionable findings. Focused validation passed: 22 tests.
Summary
sandbox doctorpreviously reported the inference route asokwhen only the provider or model was known. It now requires both fields and preserves the existing warning and recovery hint for either half-resolved state.Related Issue
Fixes #9435
Changes
ok.Type of Change
Quality Gates
Documentation Writer Review
no-docs-neededDGX Station Hardware Evidence
Verification
Signed-off-by:line and every commit appears asVerifiedin GitHubpre-commit,commit-msg, andpre-pushhooks passed, ornpm run validate:prpassed after refreshingorigin/mainwhen hooks were skipped or unavailablenpx vitest run --project cli src/lib/actions/sandbox/doctor-inference.test.tspassed 22 tests atfc7faffb8. Both half-resolved cases failed before the fix.npm testfor broad runtime or shared test-harness changes;npm run checkfor repository-wide validation or coverage changes. Command/result: not applicable; the two-file change tightens one pure diagnostic classification and adds its focused boundary tests.npm run docsbuilds without warnings (doc changes only)Signed-off-by: Rebecca Sliter 571084+rsliter@users.noreply.github.com
Summary by CodeRabbit