You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- markdownlint-disable MD041 -->
## Summary
Distinguish a Google Gemini OpenAI-compatible Chat Completions 404 from
native model-catalog validation. The report in #9298 attributes its
failure to `/v1beta/openai/models`, but v0.0.108 and current `main`
already validate Gemini models through `/v1beta/models`; the captured
`Chat Completions API: HTTP 404` instead comes from the separate runtime
route.
This change preserves fail-closed validation. It does not accept native
catalog availability as proof that the OpenAI-compatible route used by
the sandbox can serve the model. A real-key reproduction of the runtime
404 is still needed before this PR can claim to resolve provider
availability.
## Related Issue
Refs #9298
## Changes
- Carry the selected provider into validation as diagnostic-only context
without forwarding it to the network probe.
- Explain an exact Gemini Chat Completions HTTP 404 as a runtime-route
failure, not a native model-catalog failure.
- Add regression tests for provider-context isolation, credential
redaction, and the failure guidance.
- Document the distinction and the reason onboarding stops.
## Type of Change
- [ ] Code change (feature, bug fix, or refactor)
- [x] Code change with doc updates
- [ ] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)
## Quality Gates
- [x] Tests added or updated for changed behavior
- [ ] Existing tests cover changed behavior — justification:
- [ ] Tests not applicable — justification:
- [x] Sensitive paths changed (security, policy, credentials, preflight,
onboarding, inference, runner, sandbox, or messaging)
- [ ] Sensitive-path review completed or maintainer-approved waiver
recorded — reviewer/approval link/justification: Pending external review
from @cv.
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:
## DGX Station Hardware Evidence
- [ ] Tested on DGX Station
- Tested commit: Not applicable
- Station profile/scenario: Not applicable
- Result: Not applicable
- Supporting evidence: Not applicable
## Verification
- [x] PR description includes a `Signed-off-by:` line and every commit
appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run validate:pr` passed after refreshing `origin/main` when hooks
were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — `npx vitest run --project cli
src/lib/onboard/inference-selection-validation.test.ts
src/lib/onboard/setup-nim-selection.test.ts` (34 passed)
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result: Not applicable; the change
is limited to provider-specific failure diagnostics and wiring.
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only) — build
succeeded with 0 errors and 2 pre-existing warnings
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)
Additional validation: `npm run build:cli`, `npm --prefix nemoclaw run
build`, `npm run typecheck:cli`, and `npm run checks:repository` passed.
---
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
0 commit comments